MCP tool name with a dot or underscore: tools.list vs tools_list

Sume MCP tool ids use underscores; a dotted alias such as tools.list is canonicalized on call. Retired aliases map to generate_image and generate_video.

4 min readSume
All posts

Use the underscore name. Sume's live hosted tool ids are underscore names such as tools_list and generate_image, and the server canonicalizes . to _ on call, so a dotted alias like tools.list still works.

Everything here is from MCP tools and gates and Agent skills, read 2026-09-30.

Which old names were retired?

Retired aliases from the Sume MCP docs, read 2026-09-30: https://docs.sume.com/mcp/tools-and-gates
Retired or unlisted nameUse instead
image-generations_creategenerate_image
video-router_creategenerate_video
video-captions_createUnlisted; still callable by name for in-flight clients, not in tools_list

Are CLI tool ids the same?

No. The docs say CLI tool ids stay dotted, for example avatars.create, and that registry is not the hosted MCP catalog. sume tools list --json reads the CLI one.

sume tools list --json
# CLI ids are dotted, e.g. avatars.create
# hosted MCP ids are underscore, e.g. generate_image (see tools_list)

How do I get the exact contract?

Call tools_schema with name set to the underscore id. The result is the contract for that tool in the current session, including whether it needs an idempotency_key.

Does an unlisted tool count as visible?

Not in tools_list. An unlisted tool can still be called by name, but do not build new agents on it. Prefer the listed generate_image and generate_video.

Why do dotted names show up at all?

The docs say the server canonicalizes dotted names on call, so dotted aliases keep working. New agent prompts should use the underscore ids from tools_list, because that is the registry the docs treat as live. If you see tools.list in an old prompt, it still works, but updating it removes one moving part.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume