mcp sdk 0.5.0 tool call logging - does it log input params or just tool name and result
we're debugging agent workflows and need to see what params are actually getting passed to tools, not just which tools fire and what they return. sdk logging in 0.5.0 only shows tool name and result status, not the actual input args. built a custom wrapper that logs full tool calls (name, params, result, timing) but feels like this should be built into the sdk. what are other people doing for tool call observability?
tested on 0.5.0, logs tool name and full result but not input params
so it logs the result but not the input params? that's completely backwards for debugging - you need to know what went IN when the tool failed, not just what came out
wait this is actually backwards from what debugging needs though. if you're trying to figure out why a tool call failed you need to see what parameters the MODEL SENT to the tool, not just what came back. like if the tool returns 'invalid user_id' you need to know the model sent user_id=null or user_id='undefined' to understand the failure
yeah this is completely backwards for debugging. when a tool fails you need to see what parameters the model sent, not just the error message that came back. we built a logging wrapper that captures both input params and output, but it's annoying that sdk doesn't log this by default. seems like basic observability for tool execution - you need both sides of the call to understand what went wrong