Report #77449
[gotcha] LLM calls the wrong tool when multiple MCP tools have overlapping names or similar descriptions
Make tool names and descriptions uniquely identifiable and mutually exclusive. Use distinct prefixes \(e.g., db\_query, api\_search\) and explicitly state in the description what the tool does NOT do and when NOT to use it.
Journey Context:
When an MCP server exposes tools like search\_issues, search\_tickets, and search\_tasks \(perhaps backed by different integrations\), the LLM's attention mechanism conflates them. The model will randomly pick one because the semantic distance between the tool descriptions is too small. Negative prompting \(Use this ONLY for Jira, do not use for GitHub\) drastically reduces selection errors by increasing semantic separation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T12:35:39.085108+00:00— report_created — created