Make tool names stricter#204
Merged
koic merged 1 commit intomodelcontextprotocol:mainfrom Jan 3, 2026
Merged
Conversation
Follow-up to modelcontextprotocol#199 (comment) Tool names are now validated to comply with the specification. https://modelcontextprotocol.io/specification/2025-11-25/server/tools#tool-names Since the tool name is optional, `nil` value is treated as "not specified" and is ignored without validation.
koic
force-pushed
the
make_tool_names_stricter
branch
from
2df02dd to
84ff1fc
Compare
atesgoral
approved these changes
Dec 30, 2025
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
2 participants
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.
Motivation and Context
Follow-up to #199 (comment)
Tool names are now validated to comply with the specification. https://modelcontextprotocol.io/specification/2025-11-25/server/tools#tool-names
Since the tool name is optional,
nilvalue is treated as "not specified" and is ignored without validation.How Has This Been Tested?
It passes both the existing tests and the newly added tests.
Breaking Changes
This introduces stricter naming validation that complies with the specification.
Types of changes
Checklist