Default Parameters for mounted tools

[strawgate]

One thing I frequently find myself doing is creating new tools which just wrap existing tools but provide or restrict parameter values.

These MCP servers are great but they offer a large surface area and sometimes the models have a hard time with consistency

For example with the GitHub MCP server, I want the LLM to provide an issue number but be restricted to a specific repo, so I wrap the get_issues tool in a tool that only allows the LLM to provide an issue number, etc.

It would be nice if MCP adapt had the ability to limit/restrict/populate the parameters.

For example:

1. Pre-populate certain parameters leaving only the remaining parameters for the LLM
2. Restrict certain parameters, removing them from the schema and preventing them from being called

[grll]

Hi @strawgate thanks for sharing your thoughts! That sounds like it could be a nice feature for MCPAdapt as it is already wrapping the tools. Would you have a suggestion of what an API could look like for such a feature?