MCP progressive discovery: Sume tools_list, then tools_schema

Sume already supports a two-step pattern for a large tool set: call tools_list to see every tool visible in the session with safety metadata, then call tools_schema with a name to fetch one contract. That is a manual form of what the MCP roadmap calls progressive discovery.

The roadmap text is from the MCP roadmap (last updated 2026-08-22), read 2026-10-01. Sume facts are from MCP tools and gates.

What does the roadmap say?

It says servers need more options to guide clients through large sets of tools, resources and other primitives, and starts a dedicated effort around progressive discovery. It is a direction, not a finished spec, so treat the Sume tools below as the current behavior.

Which Sume tools are for discovery?

Why does the list depend on the session?

Visibility follows scope. Hosted MCP defaults to read-only visibility under OAuth mcp:read; mutating and paid tools stay hidden until the session has mcp:write or an API key. So tools_list for a read-only token is shorter than for an API key.

How should an agent use the two steps?

Have it list once, pick the tool it needs, then fetch only that schema. The docs give an example instruction: call tools_schema with name generate_image and explain idempotency_key and dry_run before submitting any paid generation. Before an expensive burst, prefer generation_admission_preview or dry_run. Client-side tool search is a related idea; see tool search with a long Sume tool list.