catalog_list shows a capability that tools_list does not

Because they answer different questions. Sume's docs say catalog_list lists public API capabilities, broader than the MCP tools, while tools_list lists every tool visible to the current session. Trust tools_list for what you can call.

Everything here is from MCP tools and gates and the MCP overview, read 2026-09-30.

Which capabilities have no MCP tool?

What should the agent call first?

Call tools_list for the session's tools and tools_schema with a name for one contract. mcp_health confirms endpoint, auth source and safety posture. Router stills and clips on MCP are generate_image and generate_video.

Call tools_list and summarize the available tools.
Then call tools_schema with name "generate_image" and explain
idempotency_key and dry_run before any paid generation.

Why might a tool be missing from tools_list?

Under OAuth with only mcp:read, mutating and paid tools are hidden until the session has mcp:write, or you use an API key. Paid calls on a read-only session return insufficient_scope.

What do I do for a REST-only product?

Call the Developer API at https://api.sume.com/v1. The docs say the hosted MCP is not full parity with the HTTP API, so plan REST for those two products.

Why does this matter to agent authors?

An agent that plans from catalog_list alone can propose a call that does not exist on MCP. The docs say hosted MCP is not full parity with the HTTP API and that the client should discover the live contract with tools_list and tools_schema. Add that as the first instruction in the agent prompt, and route the two REST-only products through your own backend.