adminScaleNodePool
Sets a node pool's node count — the ONE correct way to change how many nodes a DOKS cluster has.
Sets a node pool's node count — the ONE correct way to change how many nodes a DOKS cluster has.
The response states what the board could NOT prove: DOKS picks which nodes a shrink removes, so no particular pod is shown to survive one. See NodePool.ScaleTo.
| Tool | adminScaleNodePool |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 3 |
| Operation | POST /v1/admin/infra/clusters/{id}/nodepools/{pool}/scale |
| Product | cloud |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
count | integer | — | — | Count is the node count to set. |
id | string | — | — | ID is the DOKS cluster id, from the path. |
pool | string | — | — | Pool is the node pool, from the path. Its DO id or its name — both are unique within a cluster, and an operator reads the name off the board. |
This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.
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": "adminScaleNodePool",
"arguments": {
"count": 0,
"id": "<id>",
"pool": "<pool>"
}
}
}'Values are placeholders derived from each field's declared type. 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 |
|---|---|---|---|
cloud_adminScaleNodePool | POST /v1/admin/infra/clusters/{id}/nodepools/{pool}/scale | cloud | Sets a node pool's node count — the ONE correct way to change how many nodes a DOKS cluste |
The same capability over plain HTTP is in the cloud API reference, on https://api.hanzo.ai.
All 834 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?