get_v1_o11y_logs
GetO11yLogs returns a page of one product's logs for the caller's org.
GetO11yLogs returns a page of one product's logs for the caller's org. A normal caller sees its OWN request stream, derived from org-tagged spans; a validated platform SuperAdmin sees the product's raw infra stdout stream instead. Poll for a live tail by passing the previous response's nextCursor back as sinceNs. A well-formed product with no backing workload answers an empty page rather than an error; a malformed slug is a 400.
| Tool | get_v1_o11y_logs |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 4 |
| Operation | GET /v1/o11y/logs |
| Product | o11y |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
limit | integer | — | — | — | Limit caps the returned lines. Default 200, capped at 1000. |
product | string | — | — | — | Product is the console product slug whose logs to read, e.g. "kms". Required. |
sinceNs | integer | — | — | — | SinceNs is the nanosecond cursor from a previous response's nextCursor. Absent (0) reads the last window seconds instead. |
window | integer | — | — | — | Window is how many seconds back to read when there is no cursor. Default 900, capped at 86400. |
tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
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": "get_v1_o11y_logs",
"arguments": {
"limit": 0,
"product": "<product>",
"sinceNs": 0,
"window": 0
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. limit, sinceNs and window hold stand-ins that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so those values are this page's, not the API's. Neither the door nor the operation declares one. 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 |
|---|---|---|---|
get_v1_o11y_logs | GET /v1/o11y/logs | o11y | Returns the most recent log records in the query window, newest first — each record an… |
The same capability over plain HTTP is in the o11y API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?