createNodePool
Adds a node pool to one of the caller org's clusters and answers 201 with the created pool.
Adds a node pool to one of the caller org's clusters and answers 201 with the created pool. Only the CreateNodePoolSpec fields are forwarded; owner/provider/clusterId ride in the query exactly as Visor expects them.
| Tool | createNodePool |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 8 |
| Operation | POST /v1/clusters/{clusterId}/pools |
| Product | cloud |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
autoScale | boolean | — | — | AutoScale turns the provider's cluster autoscaler on for this pool. |
clusterId | string | — | — | ClusterID is the cluster to add the pool to, from the URL path. |
count | integer | — | — | Count is how many nodes the pool starts with. |
maxNodes | integer | — | — | — |
minNodes | integer | — | — | MinNodes and MaxNodes bound the autoscaler; they are ignored unless AutoScale is set. |
name | string | — | — | Name is the pool's name. |
provider | string | — | — | Provider is the cloud the cluster lives on (e.g. "digitalocean"). Required — Visor routes the create by it. Accepted from the body or ?provider=. |
size | string | — | — | Size is the provider size slug for each node (e.g. "s-4vcpu-8gb"). |
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": "createNodePool",
"arguments": {
"autoScale": false,
"clusterId": "<clusterId>",
"count": 0,
"maxNodes": 0,
"minNodes": 0,
"name": "<name>",
"provider": "<provider>",
"size": "<size>"
}
}
}'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_createNodePool | POST /v1/clusters/{clusterId}/pools | cloud | Adds a node pool to one of the caller org's clusters and answers 201 with the created pool |
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?