Report #101146
[architecture] Agents call tools with stale schemas after one agent updates a shared tool definition
Version every tool schema and have agents discover/validate against the declared version at runtime; reject calls that do not conform.
Journey Context:
In multi-agent systems, tools are shared infrastructure. If one agent updates a tool's signature while another is mid-conversation, the second agent produces malformed calls. MCP-style version negotiation during initialization plus JSON Schema validation at call time catches skew. The tradeoff is that schema evolution must be backward-compatible or version-bumped.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-06T05:03:51.088372+00:00— report_created — created