docs(research): required-tools MCP extension payload spec + schema (SEP-1862 availability facet) - #1012
Merged
Merged
Conversation
…schema Design record for the SEP-1862 availability-facet contribution: the shipped preflight verdict payload (specs 098/099, v0.58.0) specified as an MCP extension in two carriages — a _meta rider on tools/list (works today on 2025-11-25 via the experimental capability) and a tools/resolve response facet (the strategic fold-in). Companion JSON Schema (draft 2020-12) covers settings, request rider, batch facet, resolve facet, and per-tool verdict. Related #969
Deploying mcpproxy-docs with
|
| Latest commit: |
0e154bc
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d9b094ba.mcpproxy-docs.pages.dev |
| Branch Preview URL: | https://docs-required-tools-extensio.mcpproxy-docs.pages.dev |
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
📦 Build ArtifactsWorkflow Run: View Run Available Artifacts
How to DownloadOption 1: GitHub Web UI (easiest)
Option 2: GitHub CLI gh run download 32338751255 --repo smart-mcp-proxy/mcpproxy-go
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Design record for the standards-track contribution around required-tools preflight (spec 098/099, shipped v0.58.0):
docs/research/required-tools-mcp-extension-2026-08-20.md— theapp.mcpproxy/required-toolsextension payload spec: identifier/versioning per SEP-2133, Shape A (_metarider ontools/list; legacyexperimental-capability carriage works on today's 2025-11-25 connection) and Shape B (availability facet of a SEP-1862tools/resolveresponse), the 15-code reason enum with the gateway-class extensibility rule, inherited invariants (zero upstream I/O, point-in-time semantics, no-skew directionality, agent-token disclosure tier), risks, first consumers, and open questions.docs/research/required-tools-extension.schema.json— companion JSON Schema (draft 2020-12), machine-validated: settings, request rider, batch response facet, resolve facet, per-tool verdict (registry vs wire enum split, per-reasonretryableenforcement).Docs-only; no code changes. Cross-reviewed by opencode/gpt-5.6-sol (5 rounds, final APPROVE).
Related #969