From b625be772508e860a19a9d6f143b61f0ba85e59a Mon Sep 17 00:00:00 2001 From: olaservo Date: Sun, 16 Aug 2026 18:21:17 -0700 Subject: [PATCH] Link the dated spec revision, not /draft The surrounding sentence names 2026-07-28 as the revision that first allows an array-rooted schema, but the link pointed at /draft, which moves on to the next revision and stops matching the claim. Co-Authored-By: Claude Opus 5 --- mcp-client-rust/README.md | 2 +- weather-server-rust/README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/mcp-client-rust/README.md b/mcp-client-rust/README.md index ef98b76..9be5c44 100644 --- a/mcp-client-rust/README.md +++ b/mcp-client-rust/README.md @@ -6,4 +6,4 @@ See the [Build an MCP client](https://modelcontextprotocol.io/docs/develop/build rmcp does not validate tool output, so this client compiles each declared `outputSchema` at connect time and checks results against it — the spec's client-side SHOULD. It uses the [`jsonschema`](https://docs.rs/jsonschema) crate, which rmcp's own documentation recommends. -The two channels go to different readers: `content` is forwarded to the model, while `structured_content` is used as data — the client counts the items it returns. See [Structured Content](https://modelcontextprotocol.io/specification/draft/server/tools#structured-content). +The two channels go to different readers: `content` is forwarded to the model, while `structured_content` is used as data — the client counts the items it returns. See [Structured Content](https://modelcontextprotocol.io/specification/2026-07-28/server/tools#structured-content). diff --git a/weather-server-rust/README.md b/weather-server-rust/README.md index 647eec5..11f1ff9 100644 --- a/weather-server-rust/README.md +++ b/weather-server-rust/README.md @@ -4,6 +4,6 @@ See the [Build an MCP server](https://modelcontextprotocol.io/docs/develop/build ## Structured content -Both tools declare an `output_schema` and return `structured_content`. `get_forecast` returns an object; `get_alerts` returns a top-level JSON array, which protocol revision `2026-07-28` is the first to allow — see [Structured Content](https://modelcontextprotocol.io/specification/draft/server/tools#structured-content) in the spec. +Both tools declare an `output_schema` and return `structured_content`. `get_forecast` returns an object; `get_alerts` returns a top-level JSON array, which protocol revision `2026-07-28` is the first to allow — see [Structured Content](https://modelcontextprotocol.io/specification/2026-07-28/server/tools#structured-content) in the spec. Note that an array-rooted schema requires a `2026-07-28` client: rmcp sends it as written on every connection rather than projecting it down, so an older client rejects the tool list.