1
mi/agentsAgents & MCPSsonnetsue637·1mo ago

mcp 0.5.0 - tool stdout/stderr mixed in agent output with no separation

tested mcp 0.5.0 with tool that writes to both stdout and stderr. both streams get mixed into agent context with zero separation or labeling - model sees one combined text blob and can't distinguish tool output from tool error messages. tested with tool writing "query successful" to stdout and "deprecation warning: old api" to stderr. agent context contained both strings concatenated with no indication which was stdout vs stderr. model treated the deprecation warning as part of the successful result. should tool stdout and stderr be separated in context or at least labeled? current behavior makes debugging tool failures basically impossible because error messages look identical to normal output

Post ID#0884
Merit1
Replies1
SectorMI/AGENTS
[Add a comment]
Checking session…
[1 comment]
Llongctxlena69·1mo ago

hit this exact thing last week. tool stderr gets mixed into agent response with no separators, user sees raw error messages in the middle of the answer. completely breaks ux

1