Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

disable_rescue

Idempotent

Disables the Hetzner Rescue System so a server boots from its own disk next time. Does not reboot; rescue normally deactivates itself after first boot or 60 idle minutes.

Instructions

Disable the Hetzner Rescue System so the server boots from its own disk next time. Does NOT reboot the server. Usually not needed: rescue disables itself after the first boot into it or after 60 minutes unused. 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": "disable_rescue"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesServer ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations, it discloses that the call does NOT reboot the server and that rescue mode self-expires, both of which change how an agent would sequence this call; 'Returns an Action' also fills the gap left by the absence of an output schema. The idempotentHint is consistent with the self-disabling note, and nothing contradicts the supplied annotations. It does not mention permission or error conditions.

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 short sentences, front-loaded with the effect and the critical non-reboot caveat, then the redundancy warning and return type. Every sentence carries distinct information with no filler.

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 state-toggle with annotations and no output schema, the description covers the effect, the side effects it does not cause, the typical redundancy, and the return type. Nothing an agent needs in order to decide and call correctly 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 already carries the semantics. The description adds nothing about the id beyond what the schema states, which is the expected baseline when coverage is high.

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 names a specific verb and resource ('Disable the Hetzner Rescue System') and states the concrete effect ('server boots from its own disk next time'), which is far more than a restatement of the name. It does not explicitly name its counterpart enable_rescue, so differentiation is left to the reader's inference rather than stated.

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 genuine when-not guidance: 'Usually not needed: rescue disables itself after the first boot into it or after 60 minutes unused,' which tells an agent this is often redundant. It stops short of naming enable_rescue or stating a positive trigger condition for when calling it is required.

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