Sanitize MCP tool names and release 2.0.1 - #4
Merged
Merged
Conversation
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
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.
What changed
tools/callrouting.2.0.1and document the behavior.Why
MCP tool names can be valid under the MCP naming guidance while still being rejected by OpenRouter-backed providers. The previous collision flag also did not protect duplicate tool names: duplicate exposed names could overwrite the routing map. This keeps provider-facing names safe while retaining the raw server names for dispatch.
Verification
mcphero-2.0.1.tar.gzandmcphero-2.0.1-py3-none-any.whl.mcpheroandtests.git diff --checkpassed.The repository's full Ruff check still reports four pre-existing findings in unchanged lines of
mcphero/adapters/base_adapter.py; they are outside this patch.