Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

enable_server_backups

Idempotent

Enables automatic daily backups for a server, adding 7 rolling backup slots for a 20% price increase and returning an Action.

Instructions

Enable automatic daily backups for a server: +20% of the server price, 7 rolling backup slots (list them with list_snapshots type ["backup"] and bound_to). Returns an Action

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": "enable_server_backups"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesServer ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (which already declare non-read-only, idempotent, non-destructive, open-world), the description discloses the billing consequence (+20% of the server price), the retention model (7 rolling slots), and the return type (an Action). Cost impact and retention depth are exactly the behavioral facts an agent cannot infer from structured fields.

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?

One front-loaded sentence delivers the action, its cost, its retention behavior, a verification route, and the return type with no filler. The parenthetical is dense but every clause carries decision-relevant information.

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 one-parameter mutation with no output schema, the description covers what an agent needs: the state change, the price impact, retention limits, how to verify the result, and the return type. Nothing material is missing.

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 ('Server ID'), so the schema carries the semantics. The description's 'for a server' merely confirms what the schema already states and adds no format, range, or lookup guidance. Baseline 3 applies when schema coverage is complete.

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?

The description names a specific verb and resource ('Enable automatic daily backups for a server') and immediately distinguishes the operation from its inverse sibling disable_server_backups and from the read-only list_snapshots. An agent knows exactly what state change this produces without opening the 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?

It provides a concrete follow-up/verification path — list backups via list_snapshots with type ["backup"] and bound_to — which tells the agent how this tool relates to a sibling. It stops short of explicit when-to-use/when-not guidance against disable_server_backups, but the enable/disable pairing is unambiguous from the names.

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