{"version":"2.1.280","anchor":"eager-tool-loading-gate-for-search-matched-mcp-tools","canonical_anchor":"eager-tool-loading-gate-for-search-matched-mcp-tools","heading":"Eager tool loading gate for search-matched MCP tools","tier":"soon","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/eager-tool-loading-gate-for-search-matched-mcp-tools","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Eager tool loading gate for search-matched MCP tools\n\nA gated code path can now make certain search-matched MCP tools load eagerly instead of staying deferred\n\n**Unclear.** Whether the tengu_shiny_stardust gate controlling this behavior is switched on is unread and not stated by the finding.\n\n**What**\n\nClaude Code normally decides whether to load a tool's full details up front (eager) or defer\/hide them until needed. A new branch in that decision logic makes a tool eager if it matches certain search criteria, on top of the existing rules that MCP (Model Context Protocol) tools are always loaded eagerly and tools explicitly flagged to defer stay deferred.\n\n**Why**\n\nLoading more relevant tools eagerly can make them available sooner without waiting for deferred loading, though whether this behavior is active depends on an internal setting that hasn't been confirmed either way.\n\n- Flag `tengu_shiny_stardust`: Not enough to say (read for one account on one subscription tier against v2.1.280; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: MCP\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}