{"version":"2.1.280","anchor":"tool-routing-now-checks-a-per-tool-state-machine-before-loca","canonical_anchor":"tool-routing-now-checks-a-per-tool-state-machine-before-loca","heading":"Tool routing now checks a per-tool state machine before local\/prefetch path","tier":"internal","area":"Tool Routing","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/tool-routing-now-checks-a-per-tool-state-machine-before-loca","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Tool routing now checks a per-tool state machine before local\/prefetch path\n\nTool call routing now checks for an active per-tool state machine first, before falling back to the old local\/prefetch logic\n\n**What**\n\nThe internal logic that decides how a tool call gets dispatched now first checks whether that tool has an active state machine associated with it. For non-MCP tools (tools not provided via the Model Context Protocol) that do have one, the call is routed directly through that state machine, bypassing the previous logic based on a 'supported' flag and prefetch requests.\n\n**Why**\n\nThis changes the underlying mechanism for dispatching tool calls, letting individual tools manage their own call-handling logic via a dedicated state machine rather than going through one shared routing path.\n\n- Area: Tool Routing\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}