Skip to main content
Glama

Set the action at the threshold

gpucloud_set_server_threshold_action
Idempotent

What 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

NameRequiredDescriptionDefault
serverIdYesServer id (from gpucloud_list_servers).
onFundsExhaustedYesHIBERNATE or DELETE.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations it discloses cost ('Spends nothing'), the required permission servers:update, the account/MCP-key prerequisite, eligibility limits (spot servers reject HIBERNATE), and the full escalation timeline of notices and credit exhaustion that governs when DELETE actually fires. It also states a safety invariant ('A server is never deleted while the account has credit left') and that adding credits cancels deletion, which an agent cannot derive from destructiveHint=false alone. This is unusually rich behavioral context for a configuration mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense paragraph of semicolon-chained clauses, and the deletion timeline (three notices, 24h/1h/72h conditions) is buried mid-sentence rather than structured. The core definition of the tool and the two options is front-loaded, but the middle section could be tightened or bulleted for scanability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters, full schema coverage, and annotations covering safety hints, the description supplies nearly everything needed: prerequisites, cost, eligibility, and downstream consequences. The only gap is what the call returns or confirms after a successful change, which matters slightly since no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description earns credit by expanding each enum value far beyond its label: HIBERNATE implies a hibernation fee and immediate restart on restored balance, DELETE implies no fee, continued running until the next hour is unpaid, then stop. serverId is left to the schema, which already documents its source.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes clear this configures the fate of an hourly server when the balance runs short, with two named outcomes (HIBERNATE/DELETE) tied to the onFundsExhausted parameter. It is distinguishable from gpucloud_hibernate_server (which performs hibernation) and from gpucloud_set_auto_reload (invoked as the precondition 'no automatic reload brings it back'). It lacks an explicit leading verb like 'Sets the per-server threshold action', instead opening with the consequence, which slightly blurs the action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete selection criteria: use DELETE when the machine cannot be hibernated (spot), otherwise HIBERNATE avoids data deletion and incurs an hourly hibernation fee. The implicit framing against automatic reload sets the context in which this policy applies. It stops short of explicitly routing to siblings such as gpucloud_set_auto_reload or gpucloud_set_budget as alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources