hcloud-mcp

rollback_storage_box_snapshot

DestructiveIdempotent

Roll a Storage Box back to a chosen snapshot, permanently deleting all newer snapshots and data written since that point. Irreversible, so confirm with the user before running.

Instructions

Roll a Storage Box back to a snapshot. Deletes all newer snapshots and ALL data written since the snapshot. Irreversible; confirm with the user first. Returns an Action; poll get_storage_box_action until status is success

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>",
      "snapshot": "<snapshot>"
    },
    "name": "rollback_storage_box_snapshot"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Storage Box ID
`snapshot`	Yes	Snapshot ID or name

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.1Nov 11, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations: it specifies exactly what is destroyed (all newer snapshots and ALL data written since the snapshot) and states irreversibility, while annotations already flag destructiveHint=true and idempotentHint=true. It also discloses the async execution model and how to observe completion, which no annotation conveys.

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 clauses, front-loaded with the action, then the destructive consequence, then the safety instruction, then the return/polling semantics. No sentence is wasted and the ordering mirrors the agent's decision path.

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?

No output schema exists, and the description compensates by stating the return value (an Action) and the exact next call needed to reach success. For a destructive, asynchronous two-parameter tool, nothing an agent needs to call it 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?

Schema coverage is 100% with both parameters documented (Storage Box ID, Snapshot ID or name), so the schema carries the semantics. The description adds no extra detail such as whether the snapshot can be given by name vs ID beyond what the schema already states. Baseline 3 is appropriate.

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?

States a specific verb and resource ("Roll a Storage Box back to a snapshot"), which is clearly distinct from the create/delete/get snapshot siblings. An agent can tell immediately this is a restore operation, not a snapshot-management read.

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 the critical precondition ("Irreversible; confirm with the user first") and names the follow-up tool to poll (get_storage_box_action). It does not explicitly contrast with create_storage_box_snapshot or explain when a restore is preferable to other recovery paths, but the destructive/confirmation framing drives correct usage.

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

Deploy Server