Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_storage_box_subaccount

DestructiveIdempotent

Permanently deletes a Storage Box subaccount, disabling its login while leaving its home directory files in the main account; confirm first and poll the action status.

Instructions

Delete a subaccount (its login stops working; files in its home directory remain in the main account). 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>",
      "subaccount_id": "<subaccount_id>"
    },
    "name": "delete_storage_box_subaccount"
  }
}

Input Schema

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

Goes well beyond the annotations (destructiveHint/idempotentHint already declare the safety profile) by spelling out the real-world consequence: the subaccount login stops working while home-directory files persist in the main account. It also flags irreversibility and states the return value (an Action) plus 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?

Three short sentences, front-loaded with the action and its consequence, then the risk warning, then the return/polling note. No filler, and each sentence carries distinct information an agent needs.

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 naming the return type and the exact follow-up tool for polling. Combined with the destructive-operation warning, an agent has everything required to invoke it safely and handle the async result.

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% with both parameters documented as Storage Box ID and Subaccount ID, so the structured schema already carries the semantics. The description adds no format or constraint detail beyond that, which is the baseline expectation when the schema does the heavy lifting.

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?

Specific verb plus resource ('Delete a subaccount') with an immediate clarification that this is the subaccount, not the whole Storage Box, which cleanly distinguishes it from sibling delete_storage_box. Parenthetical consequences make the scope of the operation unambiguous.

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?

Explicitly instructs 'confirm with the user first' and directs the caller to poll get_storage_box_action until status is success, naming the exact follow-up sibling. No explicit when-not conditions are given, but for a destructive one-way operation the operational context is clear enough.

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