adminDeleteDroplet
Destroys a droplet the board has just proven is NOT a DOKS node.
Destroys a droplet the board has just proven is NOT a DOKS node. There is no snapshot-first undo for a droplet the way there is for a volume: the local disk goes with it.
| Tool | adminDeleteDroplet |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 3 |
| Operation | DELETE /v1/admin/infra/droplets/{id} |
| Product | cloud |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
disk | boolean | — | — | Disk requests a PERMANENT resize that grows the disk. DO can never resize such a droplet down again, so it defaults false — a CPU/RAM-only change, reversible. |
id | string | — | — | ID is the DO droplet id, from the path. Numeric. |
size | string | — | — | Size is the target DigitalOcean size slug on resize, 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": "adminDeleteDroplet",
"arguments": {
"disk": false,
"id": "<id>",
"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_adminDeleteDroplet | DELETE /v1/admin/infra/droplets/{id} | cloud | Destroys a droplet the board has just proven is NOT a DOKS node. |
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?