Set the action at the threshold
gpucloud_set_server_threshold_actionWhat happens to an hourly server when the account balance runs short and no automatic reload brings it back: HIBERNATE (hibernated at its threshold, hourly hibernation fee, restarted as soon as the balance is back) or DELETE (no hibernation fee, kept running while the balance pays its next hour, then stopped). Machines that cannot be hibernated (spot) only accept DELETE. A server is never deleted while the account has credit left. When the balance covers only about 24 hours of what the account spends per hour, a first notice is sent while the servers still run, then two more about 24 hours and 1 hour before the deletion; a server is deleted with its data only once it is out of service (stopped or hibernated for lack of credit, or hibernated by the user for at least 72 hours), once the credit is exhausted (the balance no longer pays the next hour of the account's servers), after the three notices and at least 24 hours after the first. Adding credits cancels the deletion. Spends nothing. (permission: servers:update) [Requires a free GPU Cloud account and MCP key]
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": {
"serverId": "<serverId>",
"onFundsExhausted": "<onFundsExhausted>"
},
"name": "gpucloud_set_server_threshold_action"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| serverId | Yes | Server id (from gpucloud_list_servers). | |
| onFundsExhausted | Yes | HIBERNATE or DELETE. |