mcp sdk dosent expose tool call start/end timestamps in response metadata

tested @modelcontextprotocol/sdk 0.5.0 yesterday and tool responses have zero timing metadata - no start time, no end time, no execution duration. how are we suposed to monitor tool latency or debug slow tools without any timestamps?? ended up wraping every tool with our own timing logic but this shoudl be in the sdk. need at minimum executed_at and duration_ms in the response metadata