Extension proposal: io.modelcontextprotocol/display-templates - #7
Open
maxiboch wants to merge 2 commits into
Open
Extension proposal: io.modelcontextprotocol/display-templates#7maxiboch wants to merge 2 commits into
maxiboch wants to merge 2 commits into
Conversation
Call-side display templates (tool-level via namespaced _meta, branch-scoped inside oneOf/anyOf subschemas) and result-side rendered display text on content-block _meta. Includes normative rendering semantics, security implications (call-side omission indicator with const-discriminator carve-out), and a reference implementation: https://github.com/maxiboch/soundboard
…ated open questions
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
1 participant
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.
Proposes a new experimental extension per CONTRIBUTING's "Proposing a
new extension": display strings for tool calls & results, solving the
dual-audience problem (compact encodings for the model, one legible
line for the human) raised in modelcontextprotocol#930 and discussed
in the #tool-annotations-ig thread "proposal for call-side string
templates".
What's in the draft:
templateunder_meta["io.modelcontextprotocol/display-templates"]on
Tool, with branch-scoped templates insideoneOf/anyOfsubschemas for one-tool-many-actions shapes
texton content-block_meta(no templating;the server knows the outcome)
...formissing/non-scalar, raw fallback, first-matching-branch
reachable, unreferenced args SHOULD be visibly counted (const
discriminators exempt), destructive confirmations SHOULD show raw
Reference implementation (runs on stock Python SDK 2.x):
https://github.com/maxiboch/soundboard
Prior discussion: #tool-annotations-ig, with guidance from
@SamMorrowDrums to target this repo as an Extensions Track proposal.
Seeking a sponsor. Open questions are listed in the draft (branch-key
spelling per SEP-2356, result-level vs per-block text, inner key
naming).