MCP tools reference

Available tools

Search aliases

search and search_operations use the same input contract. Supply optional query text, risk_tier, effect_category, and limit. The limit must be between 1 and 200, risk must be green, yellow, or red, and additional fields are rejected.

Use search for clients that prefer compact resource-style names and search_operations for clients that display descriptive operation names. Both return the same tenant-filtered operation list.

Fetch aliases

fetch and describe_operation require operation_key. Both return the same typed contract, including input_schema and execution_mode. Fetching an operation outside the credential authority returns operation_not_found without exposing broader registry access.

{
  "name": "describe_operation",
  "arguments": {"operation_key": "contacts.profile.read"}
}

Execute operation

execute_operation requires operation_key and accepts an optional arguments object that must match the fetched contract. The gateway runs only reviewed direct reads. Mutations return approval_required as a structured tool error.

Check isError before using structuredContent. Even when isError is false, validate that the operation key and tenant metadata match the outstanding request and process only the fields required by the integration purpose.

Tool-call sequence

1. Initialize the MCP connection and send notifications/initialized.
2. Call tools/list and verify the expected definitions.
3. Call search with a narrow query and optional green risk filter.
4. Call fetch or describe_operation for the selected operation key.
5. Validate direct_read and the input schema.
6. Call execute_operation with only allowed arguments.
7. Inspect isError, structuredContent, rate headers, and returned tenant metadata.