Skip to main content
Glama
lazyants
by lazyants

Delete Storage Box Subaccount

hetzner_delete_storage_box_subaccount
DestructiveIdempotent

Delete a Storage Box subaccount permanently while preserving its home directory contents.

Instructions

Delete a Storage Box subaccount permanently. Its home directory contents are not removed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesStorage Box ID
subaccount_idYesSubaccount ID
Behavior4/5

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

Annotations provide destructiveHint, idempotentHint, and openWorldHint. The description adds value by specifying that the deletion does not remove home directory contents, which is important behavioral context beyond annotations.

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?

Two concise sentences front-load the purpose and add a critical behavioral note. No redundant or unnecessary 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?

For a simple delete tool, the description covers the key effect (deletion, no removal of contents). It lacks details on reversibility or prerequisites, but annotations already provide idempotency and destructiveness hints.

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 has 100% coverage with descriptions for both parameters ('Storage Box ID' and 'Subaccount ID'). The description does not add additional meaning or format details beyond what the schema already provides.

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?

The description clearly states the action (Delete) and the resource (Storage Box subaccount), and distinguishes it from related tools like 'hetzner_delete_storage_box' by noting that home directory contents are not removed.

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?

The description implies usage for deleting a subaccount but does not explicitly state when to use it versus alternatives (e.g., deleting the entire storage box). No guidance on prerequisites or post-conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lazyants/hetzner-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server