An example result is the completed payload, not a JSON-RPC response or a pending workflow. Remove envelope fields such as jsonrpc and id and do not include task or input-required state. Multi-step interactions belong in the explicit interaction example structure.
Requirement
Section titled “Requirement”An example result is a completed result payload: it contains no JSON-RPC envelope field and no non-completed workflow field.
Details
Section titled “Details”Rule ID: mcpdesc.example.completed-result-form
Owner: mcpdesc
Surface: Example result
Kind: mcpdesc-semantic
Requirement level: must
Protocol versions: independent of the MCP protocol version
Status: internal · Enforcement: internal
Required by
Section titled “Required by”- MCP Description 0.9.0, Sections 3.6, 9.3, 10.4.4, 10.4.6, 11.3, and 11.4
- 9. Tools: req-tool-example-completed-form
-
- Resources and Resource Templates: req-resource-example-completed-form
-
- Prompts: req-prompt-example-completed-form
Based on
Section titled “Based on”- Tier 1 — MCP schema.ts and normative specification text: MCP 2026-07-28 schema.ts, InputRequiredResult (inputRequests, requestState) and Result.resultType
- Tier 1 — MCP schema.ts and normative specification text: MCP 2025-11-25 schema.ts, CreateTaskResult (task)
Envelope fields are jsonrpc, id, and error. Non-completed workflow fields are task, inputRequests, and requestState. They are excluded from the field classification of mcp.result.additional-properties.preserve.
Examples
Section titled “Examples”Invalid example
Section titled “Invalid example”Source: expected-invalid/invalid-tool-example-result-semantics.json · Selected: /tools/3/examples/task-result/result
{ "resultType": "complete", "content": [], "task": { "taskId": "task-example" }}Invalid example
Section titled “Invalid example”Source: expected-invalid/invalid-prompt-example-semantics.json · Selected: /prompts/3/examples/task-state/result
{ "resultType": "complete", "messages": [], "task": { "taskId": "task-example" }}Invalid example
Section titled “Invalid example”Source: expected-invalid/resource-example-result-semantics.json · Selected: /resources/0/examples/invalid-result/result
{ "resultType": "complete", "jsonrpc": "2.0", "task": {}, "contents": [ { "uri": "asset:///invalid.bin", "blob": "not base64" } ]}Invalid example
Section titled “Invalid example”Source: expected-invalid/invalid-completion-example-semantics.json · Selected: /prompts/2/completionExamples/bad-membership/result
{ "resultType": "complete", "completion": { "values": [ "Ada" ] }, "jsonrpc": "2.0"}Rule Source Code
Section titled “Rule Source Code”example.yaml at immutable tag v0.9.0-rc.3.