Consolidated `method`-dispatch tools return unhelpful "unknown method" errors (don't list supported methods)
還沒有人認領這個 Issue。
評估
研究方向
先從 labels.go 開始,比較其方法分派錯誤,然後檢查 pull_request_read、pull_request_review_write、issue_read、sub-issue write、actions、projects 和 ui_get 的處理器。確保未識別的方法會列出支援的值,並且會將省略的方法輸入回報為必填;驗證這兩種情況下產生的工具錯誤訊息。
由索引模型根據 Issue 內容生成。
描述
Describe the bug
The consolidated tools that dispatch on a method argument return a bare unknown method: when the method is unrecognized, without listing the valid methods. labels.go already does the helpful thing ("... Supported methods are: create, update, delete"); the other method-dispatch tools don't, so the behavior is inconsistent.
Separately, pull_request_review_write decodes arguments with mapstructure.WeakDecode (it does not use RequiredParam like the other tools), so omitting the required method produces "unknown method: " with an empty value — instead of telling the caller that method is required.
Affected tools: pull_request_read, pull_request_review_write, issue_read, sub-issue write, actions (list/get/run), projects (list/get/write), ui_get.
Affected version
Version: v1.3.0
Commit: 34227037fc48771baea9af7163e28cb6556ef287
Build Date: 2026-06-11T14:16:55Z
Steps to reproduce the behavior
- Call
pull_request_review_writewith the required method omitted, e.g.{ "owner": "o", "repo": "r", "pullNumber": 42 }. - View the output.
- Server returns (tool-result error, HTTP 200
isError):
unknown method:
(empty after the colon — method was never supplied, but the error doesn't say it's required or what the valid values are).
Or, with an unrecognized value { "method": "bogus", ... }:
unknown method: bogus
No list of supported methods. The same bare error occurs on pull_request_read, issue_read, actions_, projects_, and ui_get for any unrecognized method.
Expected vs actual behavior
Expected: the error names the supported methods (matching labels.go, e.g. unknown method: bogus. Supported methods are: create, submit_pending, delete_pending, resolve_thread, unresolve_thread), and an omitted required method reports method is required. Supported methods are: ....
Actual: a bare unknown method: with no guidance; for pull_request_review_write an omitted method yields unknown method: (empty), which reads like a routing bug rather than a missing required argument.
Logs
Tool-result error text returned by the server:
unknown method:
unknown method: bogus
- 主要語言
- Go
- 星號
- 33.1k
- 分支
- 5k
- 平均合併
- 2 天 1 小時
- 30 天內合併 PR
- 25
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
github/github-mcp-server 的其他 Issue
-
bug
難度 2/5 1-3 小時 新手友好度 84/100
github/github-mcp-server#3235 ·
-
enhancement
難度 1/5 1 小時以內 新手友好度 88/100
github/github-mcp-server#3042 · 2 則留言 ·
-
bug
難度 2/5 1-3 小時 新手友好度 72/100
github/github-mcp-server#3032 · 1 個 reaction ·
-
難度 2/5 1-3 小時 新手友好度 74/100
github/github-mcp-server#2803 · 1 則留言 ·
-
難度 2/5 1-3 小時 新手友好度 76/100
github/github-mcp-server#2740 ·
查看 github/github-mcp-server 的全部 Issue
相似的 Issue
-
難度 1/5 1 小時以內 新手友好度 60/100
github/gh-aw-mcpg#13748 ·
-
agentic-workflows
難度 2/5 1-3 小時 新手友好度 65/100
-
needs-triage
難度 2/5 1-3 小時 新手友好度 75/100
-
難度 2/5 1-3 小時 新手友好度 65/100
-
難度 2/5 1-3 小時 新手友好度 75/100
googleapis/librarian#7670 · 2 則留言 ·