modelcontextprotocol/experimental-ext-tool-annotations
Watch
1
0
Fork
You've already forked experimental-ext-tool-annotations
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge pull request #8 from modelcontextprotocol/docs/next-spec-priorities

Browse source 
docs: outline priorities for the next spec iteration
This commit is contained in:
Sam Morrow 2026-08-12 09:24:38 +02:00 • committed by GitHub
commit fecace78a9
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 46 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

46
docs/next-spec-iteration-priorities.md Normal file
View file

@ -0,0 +1,46 @@
# Priorities for the Next Specification Iteration
This is a non-binding summary of where the
[Tool Annotations Interest Group](https://modelcontextprotocol.io/community/interest-groups/tool-annotations)
believes its attention would be most useful next. Consistent with its charter,
the IG gathers use cases, evaluates proposals, and makes recommendations. It
does not set the MCP roadmap, make binding specification decisions, or own SDK
implementation; these priorities are intended to focus discussion and feedback.
## 1. Mature Existing Extension Work
Support maintainers and contributors in completing the
[planned transition of existing SEP proposals](./sep-disposition.md) into fully
fledged experimental extensions with SDK implementations. The IG should gather
use cases, coordinate review, and establish clear evidence that the community
wants and will use each extension.
## 2. Prepare Pre-flight Requests for Review
Bring the pre-flight request proposal,
[SEP-1862: Tool Resolution](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1862),
to a state where it is ready for substantive review. This remains a core
protocol proposal rather than an experimental extension, as described in the
[current SEP disposition](./sep-disposition.md).
## 3. Separate Human and Agent Content Presentation
Explore how content intended for human formatting and display can be represented
separately from content intended for agents. The goal is to let clients provide
good human-facing experiences without compromising the structured content
agents need.
[PR #7 proposes the `io.modelcontextprotocol/display-templates` experimental extension](https://github.com/modelcontextprotocol/experimental-ext-tool-annotations/pull/7)
for this purpose, covering both call-side display templates and result-side
rendered text. This belongs in the chartered discussion of tool-response
annotations and human-in-the-loop requirements.
## 4. Evaluate Annotation Proposals
Maintain an inventory of proposed annotation SEPs, evaluate how they relate to
one another and to the extension work, and provide consolidated feedback to
their authors and reviewers. The charter's current discussion list includes
[SEP-1913](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1913),
[SEP-1984](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1984),
and
[SEP-2417](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2417);
the inventory should evolve as proposals are opened, revised, or closed.