{service}_{operationId}, for example core_list_agents. The service prefix is one of core, workflow, knowledge_base, campaign, or admin, and the rest comes from the operation’s operationId.
The four meta-tools
| Tool | Purpose | Returns |
|---|---|---|
list_all_tools | List every operation by name. | Name and one-line description only. |
search_tools | Find operations by natural-language query. | Top matches, each with its input schema inline. |
describe_tool | Get full metadata for one operation. | Service, method, path, tags, and a fully resolved input schema. |
call_tool | Invoke an operation. | The upstream JSON response. |
list_all_tools()
Lists every tool exposed by the server. Each entry isname plus a one-line description only, with no input schema. Use it to browse the full catalog, then call describe_tool(name) to get the schema for a specific tool.
search_tools(query, limit=10)
Finds operations relevant to a natural-languagequery and returns the top matches, defaulting to limit=10. Unlike list_all_tools, each result carries its input schema inline, so a result is ready to invoke via call_tool without an extra round trip.
The schema returned inline by
search_tools keeps its $ref references unresolved to keep responses small. If you need a fully inlined schema before calling, fall back to describe_tool.describe_tool(name)
Fetches the full metadata and JSON Schema for a single operation byname. Use it after list_all_tools once you have picked a tool and need its input schema before calling it. Unlike search_tools, the returned inputSchema has every referenced component schema inlined under $defs.
The response includes:
| Field | Description |
|---|---|
name | The {service}_{operationId} tool name. |
description | One-line summary of the operation. |
service | The owning service: core, workflow, knowledge_base, campaign, or admin. |
method | HTTP method, for example GET or POST. |
path | The operation path, for example /agents/{agent_id}. |
tags | OpenAPI tags for the operation. |
inputSchema | The fully resolved JSON Schema for the call arguments. |
unsupported_reason | Set when the operation cannot be called via MCP, otherwise null. |
name raises an error pointing you back to list_all_tools or search_tools.
call_tool(name, arguments, organization_id)
Invokes an Anyreach API operation byname and returns the upstream JSON response.
argumentsmust conform to the operation’sinputSchema. Path, query, and header parameters are top-level keys; the request body goes under anarguments.bodyfield.organization_idis the Anyreach organization to act on behalf of. Pass it when the operation is org-scoped, which most are.
Recommended flow
Discover the operation, fetch its schema, then call it.Search or list
Use
search_tools("create an agent") to find candidate operations by intent, or list_all_tools() to browse the full catalog.Describe
Call
describe_tool(name) to get the fully resolved input schema and metadata for the operation you picked. Skip this if search_tools already returned a schema you can satisfy.Related
Coverage and limits
Which operations are exposed and what is not callable via MCP.
Connecting a client
Point an MCP client at the Anyreach server and authenticate.

