Motivation and Context

Previously, updating a Tool at runtime required explicitly calling removeTool() followed by addTool(). If listChanged was enabled, this would trigger two separate notifications to the client.

How Has This Been Tested?

Yes, I tested that the put methods work correctly. The behavior is consistent with performing a remove followed by an add, but without generating redundant notifications.

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

Additional context