Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_storage_box

DestructiveIdempotent

Permanently delete a Storage Box with all data, subaccounts, and snapshots; confirm first because deletion is irreversible and blocked when delete protection is enabled.

Instructions

Delete a Storage Box and ALL its data, subaccounts and snapshots. Irreversible; confirm with the user first. Fails if delete protection is enabled. 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": "delete_storage_box"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStorage Box 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?

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds the consequences that matter: the deletion is irreversible, it cascades to data, subaccounts and snapshots, and it is gated by delete protection. It also discloses the asynchronous return contract (an Action to poll via get_storage_box_action), 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?

Three short sentences, front-loaded with the irreversible scope, then the precondition, then the return/polling contract. Every sentence adds decision-relevant information with no repetition of the tool name or annotations.

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 destructive tool with no output schema, the description covers everything an agent needs: cascade scope, irreversibility, user confirmation, the protection precondition, and the asynchronous result plus how to follow it up. 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?

The single parameter `id` is fully documented in the schema at 100% coverage ('Storage Box ID', exclusiveMinimum 0), so the description carries no additional parameter burden. It adds nothing about the ID beyond the schema, which is the expected baseline here.

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 and immediately scopes the blast radius: 'Delete a Storage Box and ALL its data, subaccounts and snapshots.' That phrasing also separates it from delete_storage_box_snapshot and delete_storage_box_subaccount, which an agent might otherwise confuse with this tool.

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 explicit operating conditions: confirm with the user first, and the call fails if delete protection is enabled. It also names the follow-up tool get_storage_box_action for polling. It stops short of explicitly routing the agent to the narrower snapshot/subaccount deletes when only part of the box should be removed.

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