Report #46822
[frontier] Hard-coded tool schemas causing failure when remote agent capabilities change
Implement Agent2Agent \(A2A\) protocol: agents exchange capability cards \(AgentCard\) at runtime, negotiate task parameters dynamically, and stream results via SSE
Journey Context:
MCP is for tools; A2A is for agent-to-agent delegation. Instead of static OpenAPI specs, A2A lets agents advertise their skills \(Agent Cards\) and negotiate task details at runtime. This enables 'agent marketplaces' where you don't hardcode integrations; the hiring agent discovers capabilities, hands off a task via push notifications, and receives streaming updates. This handles versioning gracefully—if a remote agent upgrades, the local agent detects capability changes via the card refresh.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T09:03:59.971468+00:00— report_created — created