Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

disable_storage_box_snapshot_plan

Idempotent

Disable automatic snapshot plans for a Storage Box while preserving existing snapshots, which must be deleted manually. Returns an action to poll until the change completes.

Instructions

Disable the automatic snapshot plan. Existing automatic snapshots are kept (delete them manually). 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>"
    },
    "name": "disable_storage_box_snapshot_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStorage Box ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the key side-effect nuance: existing automatic snapshots survive the disable and must be removed separately. It also declares the async contract — returns an Action that must be polled via get_storage_box_action until status is success — 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?

Three short sentences, front-loaded with the primary action, followed by the retention caveat and the follow-up polling instruction. No filler and no repeated schema information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 correctly compensates by naming the return type (Action) and the polling follow-up, and it flags the non-obvious retention behavior. Only minor gap is the absence of any note on error or already-disabled conditions.

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% and the single 'id' parameter ('Storage Box ID', exclusiveMinimum 0) is already fully documented there. The description adds no additional meaning about the parameter, so baseline applies.

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 ('Disable the automatic snapshot plan'), which is cleanly separable from enable_storage_box_snapshot_plan and from delete_storage_box_snapshot. An agent can tell what changes and what does not 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not-to-use guidance against the sibling tools (e.g., enable vs. delete snapshot). The parenthetical 'delete them manually' implicitly signals that this tool is not the way to remove snapshots, which is useful but left for the agent to infer.

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