Repository navigation
Inconsistent parameter names #3605
Description
mcp call:
first:
{
"Arguments": {
"method": "get",
"owner": "tauri-apps",
"pull_number": 16225,
"repo": "tauri"
},
"ServerName": "github",
"ToolName": "pull_request_read"
}
output:
{
"type": "TOOL_ERROR",
"message": "missing required parameter: pullNumber"
}second:
{
"Arguments": {
"issueNumber": 16223,
"method": "get",
"owner": "tauri-apps",
"repo": "tauri"
},
"ServerName": "github",
"ToolName": "issue_read"
}
output
{
"type": "TOOL_ERROR",
"message": "missing required parameter: issue_number"
}
Activity
huong8373tt-beep commentedon Oct 30, 2026
We prepared a focused upstream PR for this issue: #3630. It accepts pull_request-style snake_case
pull_numberalongside canonicalpullNumber, accepts issue-style camelCaseissueNumberalongsideissue_number, rejects conflicting duplicates, and includes regression coverage. If maintainers prefer a different compatibility boundary, we can adjust it.