Skip to main content
Glama

Hibernate a server

gpucloud_hibernate_server

Hibernates a server: once hibernated it is billed a much lower HIBERNATION RATE (shown by gpucloud_get_server under hibernation, and returned by this tool as hibernationFee) instead of its hourly rate, for as long as it exists: tell the user this cost before hibernating; to stop paying entirely, delete the server. The system disk is kept; the WORK DISK (high-capacity local storage) is ERASED, and memory and running processes are lost: tell the user to copy important data elsewhere first (the answer carries notKept). With the backup option on, the system disk is backed up first (about 12 more minutes, billed normally; the answer carries backupFirst), then the server is hibernated automatically. The public IP address is RELEASED: a new, different one is assigned on restore, and SSH may then report a changed host key for it. Restore it later with gpucloud_restore_server: restoring takes a few minutes and depends on GPU availability. An hourly server you hibernate is kept as long as the account has credit left; once the credit is exhausted, it is deleted with its data after three notices, never within 72 h of the hibernation (tell the user). The answer carries customerHibernation (maxHours, message; deleteAt is always null: no date while credit remains). (permission: servers:hibernate) [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>"
    },
    "name": "gpucloud_hibernate_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverIdYesServer id (from gpucloud_list_servers).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Discloses a great deal beyond the annotation: work-disk erasure, memory/process loss, IP release and changed SSH host key, restore dependence on GPU availability, and credit-exhaustion deletion after three notices. However, the stated erasure of local data conflicts with the declared destructiveHint=false, so the description and annotation send an agent inconsistent safety signals.

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?

The content is valuable but packed into one long run-on paragraph with nested parentheticals about response fields (hibernationFee, notKept, backupFirst, customerHibernation). Key warnings such as data erasure and the permission note are buried mid-sentence rather than front-loaded.

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

Completeness5/5

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

For a mutation tool with no output schema, the description covers cost consequences, data loss, optional backup timing and billing, IP reassignment, restore path, and credit-exhaustion deletion. An agent has everything needed to warn the user and call the tool correctly.

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

Parameters3/5

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

There is a single parameter with 100% schema description coverage that already points to gpucloud_list_servers as the source. The description adds no further meaning about serverId (such as format, scope, or error behavior), so baseline 3 applies.

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

Purpose5/5

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

Names a specific verb and resource ('Hibernates a server') and immediately defines the distinguishing effect: reduced hibernation billing instead of hourly rate. It is clearly separable from gpucloud_restore_server (named) and from delete (named as the way to stop paying) without opening any schema.

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?

Gives explicit when-to-use (to cut cost while keeping the server) and when-not (delete to stop paying entirely), and names the counterpart gpucloud_restore_server. It does not contrast with gpucloud_stop_server, an obvious nearby alternative, leaving one gap in routing guidance.

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