hcloud-mcp

enable_storage_box_snapshot_plan

DestructiveIdempotent

Enable or replace a Storage Box automatic snapshot schedule in UTC, optionally limited by weekday or month day, and delete older snapshots beyond the configured maximum.

Instructions

Enable (or replace) the automatic snapshot plan. Runs at hour:minute UTC, optionally only on day_of_week (1=Mon..7=Sun) and/or day_of_month; null/omitted = every day. Oldest automatic snapshots beyond max_snapshots are deleted. 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>",
      "max_snapshots": "<max_snapshots>",
      "hour": "<hour>",
      "minute": "<minute>"
    },
    "name": "enable_storage_box_snapshot_plan"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Storage Box ID
`hour`	Yes	Hour (UTC)
`minute`	Yes	Minute (UTC)
`day_of_week`	No	1=Monday..7=Sunday; null = every day
`day_of_month`	No	Day of month; null = every day
`max_snapshots`	Yes	Snapshots to keep (<= the type's automatic_snapshot_limit)

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?

Annotations already declare destructiveHint=true and idempotentHint=true, but the description supplies the missing substance: the operation deletes the oldest automatic snapshots beyond max_snapshots, and '(or replace)' explains why it is idempotent. It also discloses the asynchronous return (an Action) and the polling protocol, which annotations cannot convey.

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, then schedule semantics, then the deletion consequence, then the required follow-up action. No filler or redundant framing; every sentence adds a distinct fact.

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?

With no output schema, the description still covers the return type (Action) and the required follow-up call, plus the destructive side effect of pruning old snapshots. Nothing an agent needs to invoke this correctly or handle the result 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 description coverage is 100%, so all six parameters are already documented, including the 1=Mon..7=Sun mapping and null meaning every day. The description's restatement of hour:minute UTC and the 'null/omitted = every day' rule largely duplicates the schema, adding only marginal clarification that day_of_week and day_of_month can be combined. Baseline 3 is appropriate when the schema carries the load.

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 ('Enable (or replace) the automatic snapshot plan') and immediately distinguishes itself from the sibling disable_storage_box_snapshot_plan by the enable/replace semantics. The parenthetical '(or replace)' also separates it from create_storage_box_snapshot, which is a one-off manual snapshot.

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?

Tells the agent exactly what to do after invoking: 'poll get_storage_box_action until status is success', naming the concrete sibling and the stop condition. It also explains the scheduling combinations (every day vs. day_of_week and/or day_of_month). What it lacks is an explicit when-not clause, e.g. that disabling the plan requires disable_storage_box_snapshot_plan.

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

Deploy Server