From 2c6eb7f68672b4a534cd84500b80d7527bdb0863 Mon Sep 17 00:00:00 2001 From: Sam Morrow Date: Wed, 12 Aug 2026 09:16:06 +0200 Subject: [PATCH 1/4] docs: outline next specification priorities Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3ce9ad35-1e45-451f-98f6-802946669ba8 --- docs/next-spec-iteration-priorities.md | 33 ++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 docs/next-spec-iteration-priorities.md diff --git a/docs/next-spec-iteration-priorities.md b/docs/next-spec-iteration-priorities.md new file mode 100644 index 0000000..87dde38 --- /dev/null +++ b/docs/next-spec-iteration-priorities.md @@ -0,0 +1,33 @@ +# 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. + +## 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. + +## 2. Prepare Pre-flight Requests for Review + +Bring the pre-flight request proposal +([SEP-1862](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. + +## 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. + +## 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. From 43df8e912ce6720023807de423a24d7e4d7d27b7 Mon Sep 17 00:00:00 2001 From: Sam Morrow Date: Wed, 12 Aug 2026 09:17:58 +0200 Subject: [PATCH 2/4] docs: align priorities with IG charter Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3ce9ad35-1e45-451f-98f6-802946669ba8 --- docs/next-spec-iteration-priorities.md | 43 +++++++++++++++++--------- 1 file changed, 28 insertions(+), 15 deletions(-) diff --git a/docs/next-spec-iteration-priorities.md b/docs/next-spec-iteration-priorities.md index 87dde38..e420b3e 100644 --- a/docs/next-spec-iteration-priorities.md +++ b/docs/next-spec-iteration-priorities.md @@ -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. From 59ccea3c1a8d3d70e03c29c1cf9a696cd02f30f7 Mon Sep 17 00:00:00 2001 From: Sam Morrow Date: Wed, 12 Aug 2026 09:20:43 +0200 Subject: [PATCH 3/4] docs: cite display templates proposal Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3ce9ad35-1e45-451f-98f6-802946669ba8 --- docs/next-spec-iteration-priorities.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/next-spec-iteration-priorities.md b/docs/next-spec-iteration-priorities.md index e420b3e..d055ca9 100644 --- a/docs/next-spec-iteration-priorities.md +++ b/docs/next-spec-iteration-priorities.md @@ -30,7 +30,10 @@ protocol proposal rather than an experimental extension, as described in the 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. This belongs in the chartered discussion of tool-response +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, while any specification change would still proceed through the SEP process. From 99b6214b9daa201d652033c9c8e7e97669801c6b Mon Sep 17 00:00:00 2001 From: Sam Morrow Date: Wed, 12 Aug 2026 09:22:46 +0200 Subject: [PATCH 4/4] docs: remove extension approval mechanics Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3ce9ad35-1e45-451f-98f6-802946669ba8 --- docs/next-spec-iteration-priorities.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/docs/next-spec-iteration-priorities.md b/docs/next-spec-iteration-priorities.md index d055ca9..fb89154 100644 --- a/docs/next-spec-iteration-priorities.md +++ b/docs/next-spec-iteration-priorities.md @@ -11,11 +11,9 @@ implementation; these priorities are intended to focus discussion and feedback. 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. +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 @@ -34,8 +32,7 @@ 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, while any specification change -would still proceed through the SEP process. +annotations and human-in-the-loop requirements. ## 4. Evaluate Annotation Proposals