image-generations_create is now generate_image: fix old MCP prompts

On hosted Sume MCP, the tool image-generations_create is a retired alias of generate_image. Agent prompts, allow-lists and saved playbooks that still name the old tool should be changed to generate_image, and the live name confirmed with tools_list. The Sume docs say the old name still resolves when called, but it is no longer the listed tool.

What changed

The live tool ids are underscore names, and the server canonicalizes . to _ on every call, so a dotted alias such as tools.list still works. Two retired aliases are documented: image-generations_create maps to generate_image and video-router_create maps to generate_video. Because a retired alias resolves on call but is hidden from tools_list, an allow-list that matches on the listed names will block the new tool until you add it.

Do not confuse the two image surfaces. images_create and videos_create belong to the Image 1.0 and Video 1.0 products, and they are not on hosted MCP.

Migration checklist

The change is a rename in your own instructions, not a new workflow.

• Search prompts, system messages and saved playbooks for image-generations_create.
• Replace it with generate_image, and keep idempotency_key on every call.
• Add generate_image to any tool allow-list that matches listed names.
• Call tools_list, then tools_schema with name: "generate_image", and compare the live contract with your prompt.
• Run one dry_run call before the first paid call.

Check the live list

The Sume docs tell agents to rely on tools_list and tools_schema rather than assume parity with the HTTP API. If a session cannot see generate_image, its OAuth grant is probably mcp:read only, because hosted MCP hides paid tools from read-only sessions. Re-authorize with mcp:write or use an API key.

Why it matters for agents

An agent reads its prompt literally. If the prompt says to call image-generations_create and the tool list shows generate_image, the agent may report that no image tool exists, or it may call the retired alias and succeed by luck. Neither is a state you want in production. Update the prompt once, state the new name and the idempotency rule together, and the behavior becomes predictable. The same applies to scripts that call hosted MCP directly over JSON-RPC: change the tool name in the call, not only in the docs your team reads. After the change, run tools_list in a fresh session with the same credentials your agent uses, and confirm that generate_image appears. That one call catches a scope problem before a customer-facing run does.