MCP tool-name rules (2025-11-25): do Sume's tool ids comply?

Yes. The MCP 2025-11-25 tools page says names SHOULD be 1 to 128 characters and SHOULD use only ASCII letters, digits, underscore, hyphen and dot. Sume's live ids use letters, digits, underscores and a few hyphens, and the longest one in the documented inventory, avatar-video-previews_generate_video, is 36 characters.

What the spec says

The rules are SHOULD, not MUST, and the spec adds that names are case-sensitive, should not contain spaces, commas or other special characters, and should be unique within a server. Its valid examples include getUser, DATA_EXPORT_v2 and admin.tools.list.

How Sume's ids line up

Sume's hosted MCP uses underscore ids such as tools_list and generate_image. The server canonicalizes a dot to an underscore on each call, so dotted aliases like tools.list also work. A hyphen appears inside a resource prefix, as in image-models_list.

I counted the longest id from the tools-and-gates inventory; call tools_list on a live session for the current set, because that page tells you not to assume parity with the HTTP API.

What this does not prove

Passing the spec's name rules does not mean every client accepts every name. Clients can add their own limits. If a client rejects or truncates a name, the failing client is the thing to check, not the Sume id.