Report #71166
[frontier] Multi-agent system loses state coherence because binary data and structured state are passed via unstructured text
Use MCP Resources \(not just Tools\) to expose structured state and binary data as URI-addressable objects with subscription support for real-time streaming
Journey Context:
Standard MCP usage treats it as a tool-calling layer \(text-in, text-out\). When agents need to share screenshots, audio, or structured state objects, they resort to base64-in-json hacks or external URLs outside the protocol. MCP Resources provide a first-class mechanism: servers expose state as URIs \(e.g., 'state://agent-123/memory', 'file://screenshot.png'\) with MIME types. Clients read resources to fetch binary or structured data, and subscribe to updates for live streams. This treats state like a file system, not a function call. Essential for multi-modal agent chains where Agent A captures a screenshot and exposes it via MCP Resource for Agent B \(vision-capable\) to analyze. Tradeoff: increases payload size \(base64 overhead\) and requires client support for binary rendering.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T02:01:36.386063+00:00— report_created — created