{"version":"2.1.260","anchor":"no-op-stub-tools-explain-that-chrome-browser-tools-need-no-e","canonical_anchor":"no-op-stub-tools-explain-that-chrome-browser-tools-need-no-e","heading":"No-op stub tools explain that Chrome browser tools need no enabling","tier":"internal","area":"Chrome & Browser","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/no-op-stub-tools-explain-that-chrome-browser-tools-need-no-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### No-op stub tools explain that Chrome browser tools need no enabling\n\nNo-op stub tools tell the model Chrome browser tools need no separate enabling step.\n\nTwo new no-op stub tools, `enable__mcp__claude-in-chrome` and a generic 'Browser' variant, do nothing when called. They exist to tell the model that if tools named with `Claude_Browser` are already present in the session, they're already usable, so the model should use those directly instead of wasting a call trying to \"enable\" them.\n\n- Area: Chrome & Browser\n- Names: `enable__mcp__claude-in-chrome`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}