Invalid invalidation of tool name

[Solido]

Hello!

Official spec but tool_name_validation will complain. Thanks!

Allowed characters: uppercase and lowercase ASCII letters (A-Z, a-z), digits
(0-9), underscore (_), dash (-), dot (.), and forward slash (/).

[leehack]

Hi @Solido,

Thanks for the report. Could you please provide the source of this information?

I've rechecked the specification, and I believe the current validation rule complies with it, according to https://modelcontextprotocol.io/specification/2025-11-25/server/tools#tool-names.

Feel free to let me know if I missed anything.

[Solido]

Here's another source
modelcontextprotocol/modelcontextprotocol#986

[Solido]

I think it's used to separate domain and not end_up_with_too_much_underscore ;)

[leehack]

I suspect they've decided not to update the spec with slashes, or perhaps it wasn't included in the 2025-11-25 version. I think I should stick to the official spec for now, though I'll check other SDKs later to see how they handle it. By the way, is this a critical problem you're currently facing?
https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/docs/specification/2025-11-25/server/tools.mdx#tool-names

[Solido]

I've asked directly for the reason.

Yes it can be because you want to express a separation of domain/entity/action.

Worst case / should be replaced with . => info.ticker_read would be valid