hcloud-mcp

get_storage_box_subaccount

Read-only

Retrieve a specific Storage Box subaccount by providing its Storage Box ID and subaccount ID, enabling targeted access to subaccount details.

Instructions

Get a Storage Box subaccount

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": "get_storage_box_subaccount"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Storage Box ID
`subaccount_id`	Yes	Subaccount ID

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.1Nov 11, 2026

TDQS

C2.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that — no error behavior when the ID pair is invalid, no note on permissions or whether subaccounts are returned with home-directory or access details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with zero waste, but that brevity comes from under-specification rather than discipline — there is no second clause that would earn its place by disambiguating usage.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only getter with a complete two-parameter schema and no output schema, the description should at least say what identifying information is needed and point to listing tools for discovery. Neither is present, leaving the definition adequate only in the most minimal sense.

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 both required parameters (id, subaccount_id) are documented with positive-integer constraints, so the baseline is 3. The description contributes no extra meaning such as the relationship between the box ID and the subaccount ID or how to discover a subaccount ID.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get a Storage Box subaccount" merely restates the tool name with no additional specificity — no indication of what a subaccount record contains or how it relates to the parent Storage Box. An agent can infer it is a fetch, but nothing distinguishes it in substance from list_storage_box_subaccounts or get_storage_box beyond the noun.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of the sibling list_storage_box_subaccounts as the alternative when the subaccount ID is unknown, and no prerequisites stated (e.g., that both the box ID and subaccount ID must already be known).

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

Deploy Server