Company
company: 22 operations.
Also for this capability: API · CLI · MCP · SDKs
company: 22 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.
| Tool | company |
| Address | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2, 1 required |
| Operation | GET /v1/company · GET /v1/company/register · GET /v1/company/register/summary · GET /v1/company/review |
| Product | company |
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.
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": "company",
"arguments": {
"op": "get_company"
}
}
}'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 →
The operation behind it
company dispatches to 22 operations. 4 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_company | GET /v1/company | company | Get returns the caller org's formation and the stages reachable from it, or 404 when the… |
get_company_register | GET /v1/company/register | company | Returns the platform's whole formation register, newest activity first — every org's… |
get_company_register_summary | GET /v1/company/register/summary | company | Counts the platform's formations by stage — the register's shape in one read, so a queue… |
get_company_review | GET /v1/company/review | company | Reports the founders whose KYC is not yet settled, oldest formation first, so the queue… |
The same capability over plain HTTP is in the company API reference, on https://api.hanzo.ai.
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 121 tools captured 2026-08-16.
How is this guide?