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.

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 or unlisted name | Use instead |
|---|---|
image-generations_create | generate_image |
video-router_create | generate_video |
video-captions_create | Unlisted; 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
- MCP expectedIssuer with client credentials: Sume uses an API key
MCP TypeScript SDK 2.2.0 adds expectedIssuer to machine-to-machine providers. Sume's OAuth is authorization_code only; headless agents use an API key.
- MCP listTools nextCursor: Sume returns a single page
TypeScript SDK 2.2.0 follows nextCursor in listTools(). Sume's tools/list returns a tools array with no cursor, so the walk ends after one request.
- MCP OAuth token expires: Sume's one-hour token, no refresh
Sume's hosted MCP OAuth access tokens last one hour and the server advertises only the authorization_code grant, so re-login or use an API key for long runs.
- MCP traceparent in _meta: tracing a Sume tool call end to end
MCP 2026-07-28 documents traceparent in _meta. Sume's docs don't describe reading it, so correlate with the job id and x-sume-request-id instead.
Written by Sume