put_v1_mq_streams_name
Reconfigures an existing stream; the path names the stream, and the immutable fields (storage, retention) must restate what they are.
Reconfigures an existing stream; the path names the stream, and the immutable fields (storage, retention) must restate what they are.
| Tool | put_v1_mq_streams_name |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 9 |
| Operation | PUT /v1/mq/streams/{name} |
| Product | mq |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
max_age | string | — | — | — | MaxAge caps message age, e.g. "24h" or "7d"; "0" (default) is unlimited. |
max_bytes | integer | — | — | — | MaxBytes caps the stream's total stored bytes; -1 (default) is unlimited. |
max_msg_size | integer | — | — | — | MaxMsgSize caps one message's size in bytes; -1 (default) is the broker's limit. |
max_msgs | integer | — | — | — | MaxMsgs caps the number of stored messages; -1 (default) is unlimited. |
name | string | — | — | — | Name is the stream name, unique within the org (alphanumeric, hyphens, underscores). |
num_replicas | integer | — | — | — | Replicas is the number of stream replicas (1–5); this plane runs 1. |
retention | string | — | — | — | Retention is the retention policy: limits (default), interest, or workqueue. |
storage | string | — | — | — | Storage is the storage backend: file (default) or memory. |
subjects | string[] | — | — | — | Subjects are the org-relative subjects bound to this stream (wildcards supported). Default: the stream name. |
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": "put_v1_mq_streams_name",
"arguments": {
"max_age": "<max_age>",
"max_bytes": 0,
"max_msg_size": 0,
"max_msgs": 0,
"name": "<name>",
"num_replicas": 0,
"retention": "<retention>",
"storage": "<storage>",
"subjects": [
"<subjects>"
]
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. max_bytes, max_msg_size, max_msgs and num_replicas 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 |
|---|---|---|---|
put_v1_mq_streams_name | PUT /v1/mq/streams/{name} | mq | Reconfigures an existing stream; the path names the stream, and the immutable fields… |
The same capability over plain HTTP is in the mq 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?