fix(SEP-2576): update Documentation to match Schema (Transports, Completions, Prompts, Resources) (modelcontextprotocol#2769)

* Update resource documentation to include `subscribe` optional feature

* Include now mandatory "_meta" section in tool call example. We may want
to consider a convention for this in the future to reduce boilerplate.

* Add Resource Links to the Prompts documentation

* Update completions docs to refer correctly to Resource Templates

* prettier

Author: evalstate

docs/specification/draft/basic/transports.mdx

@@ -431,6 +431,14 @@ Mcp-Param-Region: us-west1
   "id": 1,
   "method": "tools/call",
   "params": {
+    "_meta": {
+      "io.modelcontextprotocol/protocolVersion": "DRAFT-2026-v1",
+      "io.modelcontextprotocol/clientInfo": {
+        "name": "ExampleClient",
+        "version": "1.0.0"
+      },
+      "io.modelcontextprotocol/clientCapabilities": {}
+    },
     "name": "execute_sql",
     "arguments": {
       "region": "us-west1",

docs/specification/draft/server/prompts.mdx

@@ -262,6 +262,25 @@ Audio content allows including audio information in messages:
 The audio data MUST be base64-encoded and include a valid MIME type. This enables
 multi-modal interactions where audio context is important.
 
+#### Resource Links
+
+Prompt messages **MAY** include links to
+[Resources](/specification/draft/server/resources), to provide additional context or
+data without embedding the resource contents directly. In this case, the prompt message
+returns a URI that can be fetched by the client:
+
+````json
+{
+  "type": "resource_link",
+  "uri": "file:///project/src/main.rs",
+  "name": "main.rs",
+  "description": "Primary application entry point",
+  "mimeType": "text/x-rust"
+}
+
+Resource links support the same [Resource annotations](/specification/draft/server/resources#annotations)
+as regular resources to help clients understand how to use them.
+
 #### Embedded Resources
 
 Embedded resources allow referencing server-side resources directly in messages:
@@ -275,7 +294,7 @@ Embedded resources allow referencing server-side resources directly in messages:
     "text": "Resource content"
   }
 }
-```
+````
 
 Resources can contain either text or binary (blob) data and **MUST** include:
 

docs/specification/draft/server/resources.mdx

@@ -35,18 +35,24 @@ Servers that support resources **MUST** declare the `resources` capability:
 {
   "capabilities": {
     "resources": {
-      "listChanged": true
+      "listChanged": true,
+      "subscribe": true
     }
   }
 }
 ```
 
-The capability supports one optional feature:
+The capability supports two optional features:
 
 - `listChanged`: whether the server will emit notifications when the list of available
   resources changes.
+- `subscribe` : whether the server supports resource-specific update notifications
+  for resources requested through subscriptions/listen using the resourceSubscriptions
+  filter.
 
-`listChanged` is optional—servers may omit it:
+Servers may advertise either feature independently, together or neither.
+
+Serves that support neither `listChanged` or `subscribe` may omit it:
 
 ```json
 {

docs/specification/draft/server/utilities/completion.mdx

@@ -124,10 +124,10 @@ For prompts or URI templates with multiple arguments, clients should include pre
 
 The protocol supports two types of completion references:
 
-| Type           | Description                 | Example                                             |
-| -------------- | --------------------------- | --------------------------------------------------- |
-| `ref/prompt`   | References a prompt by name | `{"type": "ref/prompt", "name": "code_review"}`     |
-| `ref/resource` | References a resource URI   | `{"type": "ref/resource", "uri": "file:///{path}"}` |
+| Type           | Description                               | Example                                             |
+| -------------- | ----------------------------------------- | --------------------------------------------------- |
+| `ref/prompt`   | References a prompt by name               | `{"type": "ref/prompt", "name": "code_review"}`     |
+| `ref/resource` | References a resource URI or URI template | `{"type": "ref/resource", "uri": "file:///{path}"}` |
 
 ### Completion Results
 
@@ -157,7 +157,8 @@ sequenceDiagram
 
 ### CompleteRequest
 
-- `ref`: A `PromptReference` or `ResourceReference`
+- `ref`: A `PromptReference` or `ResourceTemplateReference`. For
+  `ResourceTemplateReference`, `uri` is a URI or URI template.
 - `argument`: Object containing:
   - `name`: Argument name
   - `value`: Current value