Upgrade a database to a larger size
resize_databaseMoves the database to a LARGER size (more vCPU, memory and included disk; see get_database_options): same data, users, names and addresses. It restarts: one to two minutes of downtime, status maintenance meanwhile (resize.to_gb set), then active with the new size_gb. The new rate applies from the next hour. Larger sizes only, there is no way back: tell the user the new price and the downtime first. Retrying the same call is safe. Scope: vms.create.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"database": "<database>",
"size_gb": "<size_gb>"
},
"name": "resize_database"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| size_gb | Yes | Memory in GB, larger than the current size_gb. | |
| database | Yes | Database id, as returned by list_databases or create_database. | |
| idempotency_key | No | Your own unique value per order. By default one is derived from the call. |