Ci

ci: 2 operations.

Also for this capability: API · CLI · MCP · SDKs

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

Tool	`ci`
Address	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	2, 1 required
Operation	`GET /v1/ci/fleet`
Product	ci

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": "ci",
         "arguments": {
           "op": "get_ci_fleet"
         }
       }
     }'

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

ci dispatches to 2 operations. 1 of them MCP names exactly as the document ids it, and that one is below; for the rest MCP has its own verb, which describe resolves.

Operation	Route	Product	Summary
`get_ci_fleet`	`GET /v1/ci/fleet`	ci	Compares what was written with what is running, one row per service along a single causal line: head, the commit on the branch; built, the image that commit produced; declared, the tag pinned in the universe repository; running, what the cluster serves.

The same capability over plain HTTP is in the ci API reference, on https://api.hanzo.ai.

All 120 tools · MCP · API reference

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

Was this page useful?

PreviousChannel NextCode