{"version":"2.1.248","anchor":"tool-dispatch-notifies-a-connector-state-listener-on-complet","canonical_anchor":"tool-dispatch-notifies-a-connector-state-listener-on-complet","heading":"Tool dispatch notifies a connector-state listener on completion","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/tool-dispatch-notifies-a-connector-state-listener-on-complet","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Tool dispatch notifies a connector-state listener on completion\n\nFinished tool calls can notify one registered connector-state listener per session.\n\n**What**\n\nWhen a tool call finishes, dispatch now calls a per-session listener after removing its abort listener, provided a condition on the dispatch result holds. The listener is registered through a new single-slot registry, so at most one listener per session receives it. The value that decides whether the call fires is computed locally and its origin is not visible from the dispatch code.\n\n**Evidence**\n\n`tool_dispatch_end`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}