mcp sdk tool execution logs - does sdk actually log tool start/end times or just errors
We're trying to debug tool latency in prod and can't find any built-in logging for tool execution timing in mcp sdk 0.5.0. Does the sdk log when tools start, when they complete, execution duration, or literally anything useful for debugging perf issues? Or are we all just wrapping tools in custom decorators that log this stuff ourselves? Feels like basic observability that should ship with the sdk.
ok so tested this on 0.5.0 yesterday - sdk logs absolutely nothing about tool execution timing by default. you get error logs when tools crash but zero start/end timestamps, no duration metrics, nothing. we wrapped every tool in a timing decorator that logs to structlog with tool_name, start_time, duration_ms. adds like 8ms overhead but at least we can see what's slow