# Tool

URL: https://docs.hanzo.ai/docs/mcp-tools/tool

> tool: 17 operations.

Also for this capability: [API](https://docs.hanzo.ai/docs/openapi/tool) · [CLI](https://docs.hanzo.ai/docs/cli/tool) · **MCP** · [SDKs](https://docs.hanzo.ai/docs/sdks)

tool: 17 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.

|               |                                                                                  |
| ------------- | -------------------------------------------------------------------------------- |
| **Tool**      | `tool`                                                                           |
| **Address**   | `https://api.hanzo.ai/v1/mcp`                                                    |
| **Method**    | `tools/call` (JSON-RPC 2.0)                                                      |
| **Arguments** | 2, 1 required                                                                    |
| **Operation** | `GET /v1/tool/activation` · `GET /v1/tool/catalog` · `GET /v1/tool/catalog/{id}` |
| **Product**   | [tool](https://docs.hanzo.ai/docs/openapi/tool)                                  |

## Arguments

| Field   | Type     | Required | Default | Values | Description                 |
| ------- | -------- | -------- | ------- | ------ | --------------------------- |
| `input` | `object` | —        | —       | —      | arguments for the chosen op |
| `op`    | `string` | **yes**  | —       | —      | —                           |

`tools/list` declares a type, a description, which fields are required and an enumerated value set for each field and nothing further, and every column above is MCP's own. This tool takes an operation name and that operation's arguments, so what the document constrains is what goes inside `input`, field by field, on the operation you name — ask `describe` for that. A `—` means MCP does not constrain the field.

## Call it

A `tools/call` carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.

```bash
curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "tool",
         "arguments": {
           "op": "list_tools"
         }
       }
     }'
```

Values are the operation's own defaults and enumerated values where it declares them, and a `<placeholder>` where neither source declares one. `tools/list` needs no credential; `tools/call` does — called without one MCP answers HTTP 200 with a JSON-RPC result whose `isError` is set and whose text says what was missing. [How to get a key →](https://docs.hanzo.ai/docs/mcp-tools#credentials)

## The operation behind it

`tool` dispatches to 17 operations. 3 of them MCP names exactly as the document ids them, and those are below; for the rest MCP has its own verb, which `describe` resolves.

| Operation                | Route                       | Product                                         | Summary                                                                                                                                                                   |
| ------------------------ | --------------------------- | ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `get_tool_activation`    | `GET /v1/tool/activation`   | [tool](https://docs.hanzo.ai/docs/openapi/tool) | Reports which tools are switched on for the caller's org and project.                                                                                                     |
| `get_tool_catalog`       | `GET /v1/tool/catalog`      | [tool](https://docs.hanzo.ai/docs/openapi/tool) | Lists the MCP servers the public registries publish, as we hold them: our canonical copy of registry.modelcontextprotocol.io, plus what we decided about each entry.      |
| `get_tool_catalog_by_id` | `GET /v1/tool/catalog/{id}` | [tool](https://docs.hanzo.ai/docs/openapi/tool) | Returns one catalog entry in full: the publisher's description, its repository and site, every package form with the runtime that launches it, and every hosted endpoint. |

The same capability over plain HTTP is in the [tool API reference](https://docs.hanzo.ai/docs/openapi/tool), on `https://api.hanzo.ai`.

---

[All 120 tools](https://docs.hanzo.ai/docs/mcp-tools/all-tools) · [MCP](https://docs.hanzo.ai/docs/mcp-tools) · [API reference](https://docs.hanzo.ai/docs/openapi)

Generated from `tools/list` on `https://api.hanzo.ai/v1/mcp` — 120 tools captured 2026-09-30.