Patrol
patrol: 26 operations.
Also for this capability: API · CLI · MCP · SDKs
patrol: 26 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.
| Tool | patrol |
| Address | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2, 1 required |
| Operation | GET /v1/patrol/camera · GET /v1/patrol/camera/{name}/stream · GET /v1/patrol/camera/{name}/stream/{ticket} · GET /v1/patrol/event · GET /v1/patrol/incident · GET /v1/patrol/incident/{name} · GET /v1/patrol/key · GET /v1/patrol/key/{name} · GET /v1/patrol/note · GET /v1/patrol/site · GET /v1/patrol/site/{name} · GET /v1/patrol/snapshot · GET /v1/patrol/tour · GET /v1/patrol/unit · GET /v1/patrol/unit/near |
| Product | patrol |
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": "patrol",
"arguments": {
"op": "get_patrol_camera"
}
}
}'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
patrol dispatches to 26 operations. 15 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_patrol_camera | GET /v1/patrol/camera | patrol | Lists the cameras a caller may OPEN. |
get_patrol_camera_by_name_stream | GET /v1/patrol/camera/{name}/stream | patrol | Mints a short-lived way in to one camera. |
get_patrol_camera_by_name_stream_by_ticket | GET /v1/patrol/camera/{name}/stream/{ticket} | patrol | Redeems a minted ticket for what opens the camera. |
get_patrol_event | GET /v1/patrol/event | patrol | Lists the feed, newest first. |
get_patrol_incident | GET /v1/patrol/incident | patrol | Lists responses. |
get_patrol_incident_by_name | GET /v1/patrol/incident/{name} | patrol | Returns one response whole: the incident, every act performed on it, and the SLA clocks those acts settled. |
get_patrol_key | GET /v1/patrol/key | patrol | Lists the key register. |
get_patrol_key_by_name | GET /v1/patrol/key/{name} | patrol | Returns one key set from the register. |
get_patrol_note | GET /v1/patrol/note | patrol | Lists internal remarks. |
get_patrol_site | GET /v1/patrol/site | patrol | Lists the estate. |
get_patrol_site_by_name | GET /v1/patrol/site/{name} | patrol | Returns one site whole: the register row plus the panel's zones and the standing hazards, which ride inside the document. |
get_patrol_snapshot | GET /v1/patrol/snapshot | patrol | Returns the whole picture in one read: sites, units with their position trails, today's tours and checkpoints, the key register, the recent feed and the open incident. |
get_patrol_tour | GET /v1/patrol/tour | patrol | Lists patrol rounds with their checkpoints — the proof-of-presence record. |
get_patrol_unit | GET /v1/patrol/unit | patrol | Lists the fleet with each unit's position trail, which is what the map draws. |
get_patrol_unit_near | GET /v1/patrol/unit/near | patrol | Answers which units can reach a site soonest. |
The same capability over plain HTTP is in the patrol 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.