GitHub issue #12977 in cline/cline, opened 2026-08-05 by boghyon, records a report that when the model calls an MCP tool via use_mcp_tool with a tool name that the connected server did not advertise, Cline forwards the call to the server unchanged, and the server then rejects it with a bare error such as "Unknown tool: 'get_note'", which is surfaced with no indication of what the valid tool names are, even though Cline already fetched and cached the server's tool catalog at connect time; the report was filed against Cline 4.1.4 (Legacy) with Anthropic Claude Opus 4.8 on a LiteLLM endpoint.
Verbatim Excerpts from Cited Records
“When the model calls an MCP tool via `use_mcp_tool` with a tool name that the connected server did not advertise, Cline forwards the call to the server unchanged.”
·
cline/cline (issue 12977 opening body, What happened section)
·
2026-08-05T21:42:44Z
·GitHub Issue ↗
“The server then rejects it with a bare error such as `Unknown tool: 'get_note'`, which is surfaced with no indication of what the valid tool names are.”
·
cline/cline (issue 12977 opening body, What happened section)
·
2026-08-05T21:42:44Z
·GitHub Issue ↗
“Because Cline already fetched and cached the server's tool catalog at connect time (tool names and input schemas), it is in a position to catch this locally and respond helpfully, but it does not.”
·
cline/cline (issue 12977 opening body, What happened section)
·
2026-08-05T21:42:44Z
·GitHub Issue ↗
“Expected: before dispatching `tools/call`, Cline validates the requested tool name against the connected server's advertised tools and, on a miss, returns a corrective error that lists the available tool names for that server (and ideally a hint to consult the "Connected MCP Servers" section).”
·
cline/cline (issue 12977 opening body, What happened section)
·
2026-08-05T21:42:44Z
·GitHub Issue ↗
Counter-record: Issue closed 2026-11-15 by linear-code[bot] as not planned. 6 comments were read. linear-code[bot] (2026-08-05) linked the report to CLINE-2867. saoudrizwan (2026-08-06) asked the reporter to try the new Next extension architecture; boghyon (2026-08-06) reported that on 4.1.6 Next every prompt results in "Not Found" and filed #13003; CoderSufiyan (2026-08-06) opened PR #13014 validating unknown tool names against the cached server catalog in McpHub.callTool() on the Legacy path before dispatching; boghyon (2026-08-09) reported new errors on 4.1.7 Next and filed #13119; boghyon (2026-08-14) reported that on 4.1.9 Next the symptom had mostly gone away because of a different fix (#13015, which stops truncated streamed tool-call JSON from being silently repaired into a wrong tool call), but that the gap this issue asks for is still open: nothing validates the tool name against the connected server's cached catalog before dispatch on either the Next or Legacy path. The closure records a not-planned decision, not a refutation of the original report. No retraction of the original report appears in the surveyed thread. The claim documents only the original report, not a verified current state.
Falsification probe: If GitHub issue #12977 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.