get_v1_o11y_reviews_id
GetAnnotationQueue returns one review queue with its pending and completed counts and its first page of items.
GetAnnotationQueue returns one review queue with its pending and completed counts and its first page of items. A queue id belonging to another org is a 404, never a cross-tenant read.
| Tool | get_v1_o11y_reviews_id |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 1, 1 required |
| Operation | GET /v1/o11y/reviews/{id} |
| Product | o11y |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
id | string | yes | — | — | ID is the annotation queue to act on, from the path. |
tools/list declares a type and a description for each field and nothing further. The Required column is taken from GET /v1/o11y/reviews/{id}, the operation this tool dispatches to — the same declaration the REST API validates against. 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. 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": "get_v1_o11y_reviews_id",
"arguments": {
"id": "<id>"
}
}
}'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 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_reviews_id | GET /v1/o11y/reviews/{id} | o11y | Returns one review queue with its pending and completed counts and its first page of… |
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?