Implemented runtime tools

[NikBellini]

This feature implements runtime tools. Basically generates the tools at runtime giving for example the possibility of showing a list of tools instead of others based on the user or other factors.

Motivation and Context

We have a very long list of tools available, but this tools must be available based on the preferences of the user. This way the LLM won't see tools that the user doesn't want or doesn't have access to, avoiding possible wrong calls.

How Has This Been Tested?

For now this has been tested in a small demo. The scenario is showing the available tools based on the user.

Breaking Changes

No, no need to update the code. This will only add a functionality

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