recordFleetSample
Records a BYO worker's live GPU utilization into the SAME series the fleet board overlays.
Records a BYO worker's live GPU utilization into the SAME series the fleet board overlays. The org is the validated principal and source/kind are fixed server-side, so a worker names only its own metrics — never another tenant or another source. Answers 202: the warehouse write is DETACHED (its own bounded context, never in the response path), so a slow or absent warehouse cannot stall a heartbeat.
| Tool | recordFleetSample |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 7 |
| Operation | POST /v1/fleet/samples |
| Product | fleet |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
gpuModel | string | — | — | — |
gpuUtil | number | — | — | GPUUtil is accelerator utilization as a fraction 0..1; the warehouse clamps anything outside that. |
gpus | integer | — | — | GPUs is how many accelerators the reading covers, GPUModel the representative model name. |
host | string | — | — | Host is the node's hostname, for display. |
memFree | integer | — | — | — |
memUsed | integer | — | — | MemUsed and MemFree are host memory in bytes. |
unit | string | — | — | Unit is the reporting node's own id — the same id it registered under, and the key the board joins this series onto. Required. |
This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.
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": "recordFleetSample",
"arguments": {
"gpuModel": "<gpuModel>",
"gpuUtil": 0,
"gpus": 0,
"host": "<host>",
"memFree": 0,
"memUsed": 0,
"unit": "<unit>"
}
}
}'Values are placeholders derived from each field's declared type. tools/list needs no credential; tools/call does — called without one the door 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
| Operation | Route | Product | Summary |
|---|---|---|---|
cloud_recordFleetSample | POST /v1/fleet/samples | fleet | Records a BYO worker's live GPU utilization into the SAME series the fleet board overlays. |
The same capability over plain HTTP is in the fleet API reference, on https://api.hanzo.ai.
All 834 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?