Methods of undeclared capabilities return -32603 instead of -32601
維護者通常 1 天內回覆
評估
這個 Issue 還沒有評估資料。
描述
On a server that only declares the tools capability, prompts/list (and the other prompt and resource methods) comes back as an Internal error instead of Method not found:
server = MCP::Server.new(name: "repro", version: "1.0.0", tools: [], capabilities: { tools: {} })
server.handle_json('{"jsonrpc":"2.0","id":1,"method":"prompts/list"}')
# => {"jsonrpc":"2.0","id":1,"error":{"code":-32603,"message":"Internal error","data":"Server does not support prompts (required for prompts/list)"}}
server.handle_json('{"jsonrpc":"2.0","id":2,"method":"unknown/x"}')
# => {"jsonrpc":"2.0","id":2,"error":{"code":-32601,"message":"Method not found","data":"unknown/x"}}
Over Streamable HTTP on the 2026-07-28 path, the first one ends up as HTTP 200 with -32603, the second as 404 with -32601. The transport spec asks for the 404 in both cases:
If the server does not implement the requested RPC method, it MUST respond with
404 Not Foundand a JSON-RPC error with code-32601(Method not found).
(Streamable HTTP, Protocol Version Header)
For a client, "the server didn't declare prompts" and "the server has no prompts/list" mean the same thing, and -32603 reads as if the server crashed. I ran into it with the conformance suite (0.2.0-alpha.12, caching scenario against a tools-only server): prompts/list returned JSON-RPC error -32603: Internal error.
The mapping is in Server#handle_request: Methods::MissingRequiredCapabilityError is re-raised with error_type: :internal_error. Raising it with error_code: JsonRpcHandler::ErrorCode::METHOD_NOT_FOUND instead looks like it would fix both protocol eras.
Seen with 1.7.0; main at 9d12f51 has the same code.
- 主要語言
- Ruby
- 星號
- 924
- 分支
- 136
- 平均合併
- 1 天 5 小時
- 30 天內合併 PR
- 37
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
modelcontextprotocol/ruby-sdk 的其他 Issue
-
Empty members in the Accept header cause a 500可能已有人在做 @koic 於 1 天前認領。 未關閉bug
難度 2/5 1-3 小時 新手友好度 82/100
modelcontextprotocol/ruby-sdk#609 ·
維護者通常 1 天內回覆
-
Error responses carry "id": null, which the MCP schema does not allow可能已有人在做 @koic 於 1 天前認領。 未關閉bug
難度 3/5 半天 新手友好度 45/100
modelcontextprotocol/ruby-sdk#606 ·
維護者通常 1 天內回覆
-
String request ids are limited to letters, digits, "_" and "-"可能已有人在做 @koic 於 1 天前認領。 未關閉bug
modelcontextprotocol/ruby-sdk#603 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Requests with "id": null are run like notifications可能已有人在做 @koic 於 1 天前認領。 未關閉bug
modelcontextprotocol/ruby-sdk#601 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Support modelcontextprotocol/experimental-ext-triggers-events可能已有人在做 @koic 於 5 天前認領。 未關閉enhancement
modelcontextprotocol/ruby-sdk#594 · 已指派 1 人 ·
維護者通常 1 天內回覆
查看 modelcontextprotocol/ruby-sdk 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 62/100
維護者通常 7 天內回覆
-
難度 2/5 1-3 小時 新手友好度 85/100
維護者通常 7 天內回覆
-
bugsnag
難度 2/5 1-3 小時 新手友好度 62/100
JoeMcB/improvcoaches#827 ·
-
難度 1/5 1 小時以內 新手友好度 72/100
TheOdinProject/curriculum#31465 ·
維護者通常 1 天內回覆
-
area: docs eco: ruby good first issue help wanted lane: free-agent roadmap size: XS type: docs
難度 1/5 1 小時以內 新手友好度 66/100
arminazimi/evergreen#465 ·
維護者通常 1 天內回覆