get_v1_o11y_metrics

GetO11yMetrics returns one product's RED series — request rate, errors, p50 and p95 latency — for the caller's org, plus that org's LLM usage rollup over the same window.

GetO11yMetrics returns one product's RED series — request rate, errors, p50 and p95 latency — for the caller's org, plus that org's LLM usage rollup over the same window. The series come from org-tagged request spans, so a tenant only ever aggregates its own traffic; a validated platform SuperAdmin sees the whole product's RED, while usage stays the caller's own org either way. A well-formed product with no backing workload answers empty series; a malformed slug is a 400.


Tool	`get_v1_o11y_metrics`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	3
Operation	`GET /v1/o11y/metrics`
Product	o11y

Arguments

Field	Type	Required	Default	Values	Description
`product`	`string`	—	—	—	Product is the console product slug to read, e.g. "kms". Required.
`range`	`integer`	—	—	—	Range is the window in seconds. Default 3600, capped at 604800 (7d).
`stepSec`	`integer`	—	—	—	StepSec is the bucket width in seconds, clamped to [30, 3600]. Absent picks ~60 buckets across the range.

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_metrics",
         "arguments": {
           "product": "<product>",
           "range": 0,
           "stepSec": 0
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. range and stepSec 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
`ListMetrics`	`GET /v1/o11y/metrics`	o11y	Lists the distinct metric names seen in a time range, each with its description, type,…

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).

Arguments

Call it

The operation behind it

On this page