Add MCP tool alias support for agent-visible names and descriptions#47
Merged
Add MCP tool alias support for agent-visible names and descriptions#47
Conversation
…ifferent description
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why
Agents may need cleaner or domain-specific tool naming/wording without requiring MCP server-side tool renames. Also, there could be conflicts in tool names when using multiple MCP servers. This keeps agent UX flexible while maintaining protocol correctness.
Summary
This PR adds support for exposing MCP tools to the agent under alternate names and descriptions, while preserving calls to the original MCP tool names.
What changed
McpConnection::withAlternateToolNames(array $map)['mcp_tool_name' => 'agent_visible_name']McpConnection::withAlternateToolDescriptions(array $map)['mcp_tool_name' => 'agent_visible_description']