{"version":"2.1.284","anchor":"wrong-name-browser-tool-calls-get-a-pointer-to-the-prefixed","canonical_anchor":"wrong-name-browser-tool-calls-get-a-pointer-to-the-prefixed","heading":"Calls to bare browser tool names now point Claude to the right tool","tier":"notice","area":"Chrome & Browser","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/wrong-name-browser-tool-calls-get-a-pointer-to-the-prefixed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Calls to bare browser tool names now point Claude to the right tool\n\nIf Claude calls a browser tool like read_page without its prefix, the error now names the correct prefixed tool to call\n\n**Unclear.** Which server prefixes count as known is not settled.\n\n**What**\n\nTools that come from MCP servers (add-ons that give Claude extra tools) have names that start with a prefix naming the server. Sometimes Claude calls a browser tool by its bare name, such as `read_page`, `find`, `form_input`, `computer` or `navigate`. When exactly one loaded tool ends with that name, has a known prefix and accepts the arguments given, the error message now tells Claude which tool to call instead.\n\nIf that tool is deferred (loaded only on demand), the message also tells Claude to load it first with `ToolSearch` using `select:`. Before, the only hint of this kind was about names that differed in upper or lower case.\n\n**Why**\n\nClaude gets back on track faster after guessing a browser tool's name, instead of trying again blind.\n\n- Area: Chrome & Browser\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}