Add Tool Arguments to Instrumentation Data

[duboff]

Include the tool arguments in instrumentation callback data when tools/call is invoked. This allows consumers to track which arguments were passed to each tool call for analytics and debugging purposes.

Motivation and Context

Include tool arguments in instrumentation callback data when tools/call is invoked, allowing consumers to track which arguments were passed to each tool call, useful for debugging and analysis.

How Has This Been Tested?

Yes, tested with the Chattermill MCP (proprietary).

Breaking Changes

No breaking changes.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

[koic]

Looks good to me!