Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_snapshot

Create a snapshot or backup image from a server disk to preserve data; snapshots survive server deletion, while backups require backups enabled and are removed with the server.

Instructions

Create an image from a server's disk. type snapshot (default) is independent of the server and survives its deletion; billed per GB-month. type backup needs backups enabled and is deleted with the server. Shut the server down first for a consistent disk. Returns the image (status creating) and an Action; the server is locked until it finishes

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": {
      "id": "<id>"
    },
    "name": "create_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesServer ID
typeNoDefault snapshot
labelsNo
descriptionNoImage description (auto-generated if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: snapshot survives server deletion and is billed per GB-month, backup is deleted with the server, and the server is locked until the action finishes. It also discloses the return shape (image with status creating plus an Action), which no output schema provides. Nothing here contradicts readOnlyHint=false / destructiveHint=false.

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

Conciseness5/5

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

Four dense sentences, each carrying distinct information (purpose, type tradeoff, precondition, return/lock semantics) with the core action front-loaded. No filler or restatement of the tool name.

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 mutating, non-idempotent, open-world tool with no output schema, the description covers what is created, the cost/lifecycle consequences, the safety prerequisite, and the asynchronous completion signal. An agent has everything needed to invoke it correctly and set expectations.

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 75%, and the description meaningfully enriches the enum: it explains the lifecycle and cost consequences of `snapshot` versus `backup`, well beyond the schema's bare "Default snapshot." The `labels` and `description` parameters remain undocumented in the prose, but they are low-risk and self-explanatory.

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?

Opens with a specific verb+resource: "Create an image from a server's disk." It then forks the resource into its two concrete variants (snapshot vs backup), so an agent can tell exactly what is produced and how it differs from a storage-box snapshot sibling.

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 selection guidance between the two `type` values, including preconditions for backup ("needs backups enabled") and an operational prerequisite ("shut the server down first for a consistent disk"). It does not name sibling tools such as create_storage_box_snapshot, so there is no explicit routing away from alternatives.

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

Deploy Server

Other Tools