patch_v1_o11y_reviews_id
UpdateAnnotationQueue changes a review queue's name, description or score-config set. A field the request omits is left alone.
UpdateAnnotationQueue changes a review queue's name, description or score-config set. A field the request omits is left alone. A name another queue in the same project already uses is a 409; a queue id belonging to another org is a 404.
| Tool | patch_v1_o11y_reviews_id |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 4 |
| Operation | PATCH /v1/o11y/reviews/{id} |
| Product | o11y |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
description | string | — | — | — | Description replaces the free text when present, up to 512 characters. |
id | string | — | — | — | ID is the annotation queue to update, from the path. |
name | string | — | — | — | Name replaces the queue's display handle when present, 1–128 printable characters and unique within the project. |
scoreConfigIds | string[] | — | — | — | ScoreConfigIDs replaces the whole score-config set when present. |
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": "patch_v1_o11y_reviews_id",
"arguments": {
"description": "<description>",
"id": "<id>",
"name": "<name>",
"scoreConfigIds": [
"<scoreConfigIds>"
]
}
}
}'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 |
|---|---|---|---|
patch_v1_o11y_reviews_id | PATCH /v1/o11y/reviews/{id} | o11y | Changes a review queue's name, description or score-config set. |
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?
get_v1_o11y_status
GetO11yStatus reports whether a product's service is live: an in-cluster health probe with its measured latency, fused with the per-replica up inventory.
patch_v1_o11y_reviews_id_items_itemId
UpdateAnnotationQueueItem moves one queue item between PENDING and COMPLETED and sets its assignee. Completing an item stamps its completedAt.