Cache tool call params

[matteo8p]

We cache tool parameters after you run the tool

Motivation and Context

This is a quality of life improvement. The tool parameters get saved when you run the tool. That way, when you switch in and out of a tool, the parameters are saved and can be re-used.

See this suggestion: https://github.com/modelcontextprotocol/inspector/issues/609

How Has This Been Tested?

Did a functional test. The params are saved after tool execution.

Breaking Changes

No

Types of changes

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

Checklist

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

Additional context

[pamelafox]

@olaservo I wondered about that so I did some searching, and it seems like localStorage allows quite a range of key names: https://stackoverflow.com/questions/19897374/can-an-html5-localstorage-key-be-any-string Have you seen limitations in practical use, however?