Tools
Conformance rewrites tool-name validation against the actual spec prose after enforcing a stale SEP for months
modelcontextprotocol/conformance#380 (merged 2026-09-06T20:05Z) fixes `tools-name-format`, which had been enforcing SEP-986 markdown — 64 characters, `/` permitted — instead of the 2025-11-25 and draft spec prose of 1 to 128 characters restricted to `[A-Za-z0-9_.-]`. It also downgrades SHOULD violations from FAILURE to WARNING per the repo's AGENTS.md and gates the check to 2025-11-25 and later via `toolNameFormatCheckApplies()`, so 2025-03-26 and 2025-06-18 runs stop false-failing. The PR deliberately files no `sep-986.yaml`, on the grounds the requirement is core spec rather than SEP traceability.
Source
↳ Follow the thread