Sume MCP tool names: tools.list or tools_list, which one to call?

Use the underscore ids that tools_list returns, such as tools_list, generate_image and jobs_wait. Sume's docs say the server also canonicalizes dotted aliases like tools.list to the underscore name, so a dotted call usually works. But write the underscore name in prompts and configs, because that is the live id, and because your client may add its own prefix.

Three places a name can differ

The overview page on Sume MCP states the first two rows. The prefix row comes from Sume's server instructions, which tell agents to use the namespaced name their client shows.

What goes wrong

The common failure is a prompt that hard-codes one form while the client shows another. If your client lists sume-generate_image and your prompt says generate_image, the agent may guess wrong. Fix it by pasting names from the client's own tool list into the prompt, not from memory.

Also do not invent names. Sume's tool notes say that a name absent from tools_list is not available. Tools from other vendors' inventories will not exist here, and a tools_schema call on an unknown name fails closed instead of guessing an alias.

• Run tools_list after connecting and copy the ids you need.
• Pass the snake_case id as name to tools_schema.
• Do not write dotted names into saved prompts or scripts.

The tradeoff

The alias is a convenience for clients that prefer dotted names, and it is not a reason to mix styles. Keeping one style costs nothing, and it means a failed call tells you something real, such as a missing scope, rather than a spelling problem.

One more habit helps agents that run unattended: have them call tools_list at the start of a session and read the names back, instead of relying on a name from a previous run. Sume's quickstart tells you the same thing, that live ids use underscores and dotted aliases also work, and that tools_list is the call that shows what this session can reach.