get_workflow_instructions and models_explore are not on Sume's MCP

If an agent prompt, a saved skill or a tutorial tells a model to call get_workflow_instructions, models_explore, media_import_url or remove_background on Sume's hosted MCP server, those calls will fail: the docs list these four names as not available there. The Sume equivalents are different tools. Cutouts are rmbg_create, and the social URL mirror is media-imports_create. For model and workflow discovery, use tools_list, tools_schema and catalog_list.

The four names come from another vendor's MCP server. Prompts written for that server get copied into new agent setups, and the model then tries tools that Sume never registered. This page gives the mapping, so you can fix the prompt rather than the server.

The same pattern shows up with other imported skills. A rule of thumb is that any tool name which does not appear in tools_list for your own session does not exist for that session, no matter where the prompt came from. Ask the model to list tools first and to stop when a name is missing, rather than to try variants of the name.

Old name to Sume tool

The right fix depends on what the old prompt wanted to do. Match the intent, not the name.

Read the middle column as the test for each old line in your prompt. If the intent is still needed, replace the name. If the intent was only about a step that Sume does by itself, delete the line. For example, a Sume agent does not need a separate instruction tool, because the tool descriptions and the server instructions carry the routing rules.

Discovery is live, not a static instruction tool

Discovery on Sume is built into the server and is meant to be used live. tools_list returns every tool that the current session can see, with its safety metadata. tools_schema takes one name and returns that tool's contract. The docs say to always use the two rather than assume parity with the HTTP API or with any other server. A model that reads the schema before a paid call sees which fields are required, which includes idempotency_key for paid tools.

A short tip for model discovery: the router stills and clips tools default to sume/auto when payload.model is omitted, unless the user named a family. That means an agent does not have to explore models before a normal request. It only needs the model tools when the person asks for one in particular, and then image-models_list, image-models_get and video-router_models give the live list instead of a remembered one.

Names and visibility

Two details save time. First, tool ids use underscores, and a call with dots, such as tools.list, still works because the server canonicalizes . to _. Second, what you see depends on the grant: a read-only OAuth session lists only read tools, and a write grant or an API key lists the full hosted set.

When the catalog and the tool list disagree

catalog_list is the place for capabilities, and it can show things that have no MCP tool. That is expected. Sume Image 1.0 and Video 1.0, called images_create and videos_create, are REST-only; on MCP the router tools are generate_image and generate_video. If catalog_list shows a capability that tools_list does not, call the Developer API for it instead of looking for a missing tool name.

Treat that mismatch as information, not as a bug. It lets an agent say honestly that a capability exists on the HTTP side but not in the tool list, and offer the REST route as the next step.

Here is a short replacement for an old "discover first" instruction that you can paste into an agent prompt:

Test the prompt in a read-only OAuth session first. If the model reaches for a write tool, the call returns insufficient_scope, and you learn that the prompt assumed a grant that the session does not have.

Before using any Sume tool, call tools_list once. For a tool you plan to use,
call tools_schema with its name. Never guess tool names. For a paid tool,
send a unique idempotency_key and run dry_run=true first.
To cut out a subject use rmbg_create. To mirror a social video use
media-imports_create, then jobs_wait, then media-imports_get.

Where to check

Read MCP tools and gates for the full inventory and the "Not on hosted MCP" list, and MCP OAuth and API keys if a tool is missing because the session has no Write scope.