Report #3581
[gotcha] MCP tool dumps a huge payload and silently truncates the conversation context
Paginate or summarize responses server-side; for bulky data return a pointer or URI and expose a separate read\_chunk or get\_summary tool.
Journey Context:
Browser MCP servers that return full HTML, or search tools that return large JSON arrays, can fill the context window in a single turn and leave no room for the model to reason. A real Roo Code issue showed a Playwright MCP mode navigating to a page and getting stuck because the returned page exceeded the token budget. The common mistake is forwarding raw upstream API output unchanged. The reliable pattern is to shape output for the model: truncate with a clear indicator, paginate, or store large data behind a pointer so the model pulls only what it needs.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T17:35:17.998413+00:00— report_created — created