-
Notifications
You must be signed in to change notification settings - Fork 60
Fix tools-name-format for spec Tool Names SHOULD rules on 2025-11-25+ #380
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
canardleteer
wants to merge
4
commits into
modelcontextprotocol:main
Choose a base branch
from
canardleteer:fix/379-sep-986-tool-names
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+293
−33
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
e73d18b
fix(tools-list): align tools-name-format with 2025-11-25 spec prose
canardleteer c9acab6
test(tools-list): cast Connection.request mock for tsgo typecheck
canardleteer af9d991
test(tools-list): pin WARNING to offending tool name in negative test
canardleteer f1e4395
test(tools-list): rename negative fixture to invalid-tool-names
canardleteer File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,91 @@ | ||
| #!/usr/bin/env node | ||
|
|
||
| /** | ||
| * Negative test server for spec Tool Names SHOULD rules (2025-11-25+). | ||
| * | ||
| * AGENTS.md negative-fixture pattern: bypass SDK registerTool validation via | ||
| * setRequestHandler(ListToolsRequestSchema) so tools/list advertises a name | ||
| * that violates core spec prose at #tool-names. Proves tools-name-format emits | ||
| * WARNING (SHOULD-level per AGENTS.md), not FAILURE. everything-server unchanged. | ||
| * | ||
| * ## Why this file is not named after SEP-986 | ||
| * | ||
| * Tool name format rules trace to [SEP-986](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/986) | ||
| * (opened 2025-07-16), but the **authoritative rules live in dated spec prose**, | ||
| * not the SEP markdown artifact. That split is a process wart worth preserving: | ||
| * | ||
| * - **SEP-986 markdown** (`seps/986-specify-format-for-tool-names.md`) still | ||
| * documents stale rules: 1–64 chars, `[A-Za-z0-9_./-]` including `/`. The | ||
| * finalized SEP file was **never updated** after spec integration. | ||
| * - **Integrated spec** ([PR #1603](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1603), | ||
| * Oct 2025) landed different prose in draft, then **2025-11-25** `#tool-names`: | ||
| * 1–128 chars, `[A-Za-z0-9_.-]` only (no `/`). | ||
| * - **Conformance #240** incorrectly encoded the stale SEP markdown (64 + `/`, | ||
| * FAILURE severity). This suite follows the integrated spec diff per AGENTS.md; | ||
| * see `tools.ts` block comment and `specReferences` (core URLs first, SEP links | ||
| * context-only). There is intentionally **no `sep-986.yaml`** traceability row. | ||
| * | ||
| * Naming the fixture after the SEP would imply traceability we deliberately | ||
| * declined — and would obscure that the SEP artifact and published spec diverged. | ||
| */ | ||
|
|
||
| import { Server } from '@modelcontextprotocol/sdk/server/index.js'; | ||
| import { StreamableHTTPServerTransport } from '@modelcontextprotocol/sdk/server/streamableHttp.js'; | ||
| import { ListToolsRequestSchema } from '@modelcontextprotocol/sdk/types.js'; | ||
| import express from 'express'; | ||
|
|
||
| function createServer() { | ||
| const server = new Server( | ||
| { name: 'invalid-tool-names', version: '1.0.0' }, | ||
| { capabilities: { tools: {} } } | ||
| ); | ||
|
|
||
| server.setRequestHandler(ListToolsRequestSchema, async () => ({ | ||
| tools: [ | ||
| { | ||
| name: 'bad tool name', | ||
| description: 'Deliberately invalid tool name for conformance testing', | ||
| inputSchema: { type: 'object' } | ||
| }, | ||
| { | ||
| name: 'valid_tool', | ||
| description: 'A conformant tool name', | ||
| inputSchema: { type: 'object' } | ||
| } | ||
| ] | ||
| })); | ||
|
|
||
| return server; | ||
| } | ||
|
|
||
| const app = express(); | ||
| app.use(express.json()); | ||
|
|
||
| app.post('/mcp', async (req, res) => { | ||
| try { | ||
| const server = createServer(); | ||
| const transport = new StreamableHTTPServerTransport({ | ||
| sessionIdGenerator: undefined | ||
| }); | ||
| await server.connect(transport); | ||
| await transport.handleRequest(req, res, req.body); | ||
| } catch (error) { | ||
| if (!res.headersSent) { | ||
| res.status(500).json({ | ||
| jsonrpc: '2.0', | ||
| error: { | ||
| code: -32603, | ||
| message: `Internal error: ${error instanceof Error ? error.message : String(error)}` | ||
| }, | ||
| id: null | ||
| }); | ||
| } | ||
| } | ||
| }); | ||
|
|
||
| const PORT = parseInt(process.env.PORT || '3009', 10); | ||
| app.listen(PORT, '127.0.0.1', () => { | ||
| console.log( | ||
| `Invalid tool names negative test server running on http://localhost:${PORT}/mcp` | ||
| ); | ||
| }); | ||
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.