MCP connector tools
Find complete current tool schemas and check permission, cost and review requirements.
The developer catalogue lists the release's registered MCP tools with complete input schemas. The older 37-tool list is not the current catalogue.
Call MCP tools/list and use its names and schemas. An old count is not a test of full product coverage. Tools still require permissions and normal account access.
| Discovery | What to check |
|---|---|
tools/list |
Names, descriptions, required and optional inputs, and hints. |
customer_operation_catalogue |
New customer operations, consent scope, cost class, review and execution availability. |
| Developer catalogue | Search by area and inspect full schemas. |
| Tool response | Actual status, errors, action or job reference and review link. |
Choose direct tools for records, reports and saved context. Use separately consented management for ordinary changes. Request another agent only when a specialist run or continued processing is useful.
A prepared review has not executed. A queued job has not finished. Fetch the result and report the actual state.
Explicit writing, research and external actions can use paid work. Ordinary reads do not invoke another reasoning agent. Unavailable execution remains unavailable.
See MCP tool groups and capability discovery, How protected MCP actions reach you for approval and Permissions and limits.