Implementation of SEP-986: Specify Format for Tool Names #900
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
|
Sorry about all the changes after I opened the PR. I thought it was ready, but I guess it wasn't 😅 Should be ready to go now. |
cliffhall
reviewed
Aug 25, 2025
src/shared/toolNameValidation.ts
Outdated
| } | ||
| console.warn("Tool registration will proceed, but this may cause compatibility issues."); | ||
| console.warn("Consider updating the tool name to conform to the MCP tool naming standard."); | ||
| console.warn("See SEP: Specify Format for Tool Names for more details."); |
There was a problem hiding this comment.
Consider including a URL to this SEP here.
There was a problem hiding this comment.
Good idea 👍 Done.
kentcdodds
commented
Aug 25, 2025
- Add comprehensive tool name validation utility with regex patterns - Validate tool names against SEP-0001 specification requirements - Support valid characters: lowercase letters, numbers, hyphens, underscores - Enforce length limits (1-64 characters) and naming conventions - Generate appropriate warnings for non-compliant tool names - Add extensive test coverage with Jest spies for console methods - Integrate validation into McpServer.registerTool() method - Update test suite to cover all validation scenarios - Add documentation and examples for tool name validation This ensures all registered tools comply with the Model Context Protocol specification for tool naming, improving interoperability and consistency.
kentcdodds
force-pushed
the
cursor/validate-tool-name-format-and-add-tests-beb1
branch
from
0546db5 to
f807421
Compare
felixweinberger
force-pushed
the
main
branch
from
0845a57 to
c94ba4b
Compare
- Adjusted validation logic and regex to accept tool names between 1 and 64 characters - Updated test cases to reflect new character length requirements - Modified warnings to align with the updated maximum length modelcontextprotocol/modelcontextprotocol#986 (comment)
5 tasks
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.
Motivation and Context
modelcontextprotocol/modelcontextprotocol#986
How Has This Been Tested?
Unit tests
Breaking Changes
None, but console warnings may appear for SDK users who have names that do not satisfy the SEP.
Types of changes
Checklist
Additional context
FYI, I used Cursor background agents for this.
Very open to feedback to adjust this implementation.