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

docs: align priorities with IG charter

Browse source 
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 3ce9ad35-1e45-451f-98f6-802946669ba8
This commit is contained in:
Sam Morrow 2026-08-12 09:17:58 +02:00
commit 43df8e912c
No known key found for this signature in database
1 changed files with 28 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

43
docs/next-spec-iteration-priorities.md
View file

@ -1,33 +1,46 @@
# Priorities for the Next Specification Iteration
This is a non-binding summary of where the Tool Annotations Interest Group
believes its attention would be most useful next. The IG has no formal remit to
set the MCP roadmap or determine the disposition of SEPs; these priorities are
intended to focus discussion, implementation, and feedback.
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
Complete the transition of existing SEP proposals into fully fledged
experimental extensions. Each extension should have SDK implementations and
clear evidence that the community wants and will use it before it is proposed
for graduation.
Support maintainers and contributors in completing the
[planned transition of existing SEP proposals](./sep-disposition.md) into fully
fledged experimental extensions. The IG should gather use cases, coordinate
review, and establish clear evidence that the community wants and will use each
extension. Before an Extensions Track SEP is reviewed,
[SEP-2133](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/seps/2133-extensions.md)
requires at least one reference implementation in an official SDK.
## 2. Prepare Pre-flight Requests for Review
Bring the pre-flight request proposal
([SEP-1862](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1862))
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.
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.
agents need. This belongs in the chartered discussion of tool-response
annotations and human-in-the-loop requirements, while any specification change
would still proceed through the SEP process.
## 4. Evaluate Annotation Proposals
Gather the proposed annotation SEPs, evaluate how they relate to one another and
to the extension work, and provide consolidated feedback to their authors and
reviewers.
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.