Merge branch 'main' into chore/elicitation-schema-depth-limit

Author: LucaButBoring

docs/docs.json

@@ -128,6 +128,7 @@
               "links/sdks/kotlin",
               "links/sdks/python",
               "links/sdks/ruby",
+              "links/sdks/rust",
               "links/sdks/swift",
               "links/sdks/typescript"
             ]
@@ -241,6 +242,7 @@
               "links/sdks/kotlin",
               "links/sdks/python",
               "links/sdks/ruby",
+              "links/sdks/rust",
               "links/sdks/swift",
               "links/sdks/typescript"
             ]
@@ -353,6 +355,7 @@
               "links/sdks/kotlin",
               "links/sdks/python",
               "links/sdks/ruby",
+              "links/sdks/rust",
               "links/sdks/swift",
               "links/sdks/typescript"
             ]
@@ -468,6 +471,7 @@
               "links/sdks/kotlin",
               "links/sdks/python",
               "links/sdks/ruby",
+              "links/sdks/rust",
               "links/sdks/swift",
               "links/sdks/typescript"
             ]

docs/links/sdks/rust.mdx

@@ -0,0 +1,10 @@
+---
+title: Rust SDK
+url: https://github.com/modelcontextprotocol/rust-sdk
+icon: rust
+---
+
+<Card
+  title="Rust SDK"
+  href="https://github.com/modelcontextprotocol/rust-sdk"
+/>

docs/specification/2025-06-18/basic/utilities/progress.mdx

@@ -78,11 +78,9 @@ sequenceDiagram
     Sender->>Receiver: Method request with progressToken
 
     Note over Sender,Receiver: Progress updates
-    loop Progress Updates
-        Receiver-->>Sender: Progress notification (0.2/1.0)
-        Receiver-->>Sender: Progress notification (0.6/1.0)
-        Receiver-->>Sender: Progress notification (1.0/1.0)
-    end
+    Receiver-->>Sender: Progress notification (0.2/1.0)
+    Receiver-->>Sender: Progress notification (0.6/1.0)
+    Receiver-->>Sender: Progress notification (1.0/1.0)
 
     Note over Sender,Receiver: Operation complete
     Receiver->>Sender: Method response

docs/specification/2025-06-18/server/tools.mdx

@@ -273,8 +273,7 @@ or data using a suitable [URI scheme](./resources#common-uri-schemes). Servers t
 
 **Structured** content is returned as a JSON object in the `structuredContent` field of a result.
 
-For backwards compatibility, a tool that returns structured content SHOULD also return functionally equivalent unstructured content.
-(For example, serialized JSON can be returned in a `TextContent` block.)
+For backwards compatibility, a tool that returns structured content SHOULD also return the serialized JSON in a TextContent block.
 
 #### Output Schema
 

docs/specification/draft/basic/utilities/progress.mdx

@@ -78,11 +78,9 @@ sequenceDiagram
     Sender->>Receiver: Method request with progressToken
 
     Note over Sender,Receiver: Progress updates
-    loop Progress Updates
-        Receiver-->>Sender: Progress notification (0.2/1.0)
-        Receiver-->>Sender: Progress notification (0.6/1.0)
-        Receiver-->>Sender: Progress notification (1.0/1.0)
-    end
+    Receiver-->>Sender: Progress notification (0.2/1.0)
+    Receiver-->>Sender: Progress notification (0.6/1.0)
+    Receiver-->>Sender: Progress notification (1.0/1.0)
 
     Note over Sender,Receiver: Operation complete
     Receiver->>Sender: Method response

docs/specification/draft/server/tools.mdx

@@ -273,8 +273,7 @@ or data using a suitable [URI scheme](./resources#common-uri-schemes). Servers t
 
 **Structured** content is returned as a JSON object in the `structuredContent` field of a result.
 
-For backwards compatibility, a tool that returns structured content SHOULD also return functionally equivalent unstructured content.
-(For example, serialized JSON can be returned in a `TextContent` block.)
+For backwards compatibility, a tool that returns structured content SHOULD also return the serialized JSON in a TextContent block.
 
 #### Output Schema