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: cite display templates proposal

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:20:43 +02:00
commit 59ccea3c1a
No known key found for this signature in database
1 changed files with 4 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -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 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 separately from content intended for agents. The goal is to let clients provide
good human-facing experiences without compromising the structured content 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 annotations and human-in-the-loop requirements, while any specification change
would still proceed through the SEP process. would still proceed through the SEP process.