Internal refactor of MCP handlers #2005
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request refactors and standardizes the internal API and method naming conventions for MCP handlers. Specifically, it takes what used to be two methods and a JIT-generated handler and refactors them into three handlers:
_list_tools_mcp: previously_mcp_list_tools, this method is the registered handler with the low-level MCP server and returns the handler result in MCP-native format_list_tools_middleware: previously_list_tools, this method applies MCP middleware_list_tools: previously generated dynamically in_list_tools_middleware, this is the core handler that is responsible for listing toolsThis makes it more clear where responsibility lies and avoids dynamically generating new functions unnecessarily, which made debugging more difficult.
In addition, an internal parameter
via_serverwas renamed toapply_filtering.