Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_storage_box_subaccounts

Read-only

List a Storage Box's subaccounts by ID to view usernames, home directories, access settings, and server FQDNs. Filter or sort results to inspect account access.

Instructions

List subaccounts of a Storage Box (username, home_directory, access settings, server FQDN)

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

Input Schema

NameRequiredDescriptionDefault
idYesStorage Box ID
nameNo
sortNoSort fields with optional direction, e.g. ["name:asc", "created:desc"]
usernameNo
label_selectorNoLabel selector, e.g. env=prod

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the return-field inventory, which is modest but useful context; it says nothing about pagination, result caps, or whether subaccounts can be numerous, so it goes only slightly beyond the structured data.

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

Conciseness4/5

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

A single front-loaded sentence with the verb and resource first and the returned fields in parentheses — zero wasted words. It is arguably over-compact given the missing usage and parameter guidance, but nothing in it needs cutting.

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

Completeness3/5

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

For a read-only listing tool with no output schema, naming the returned fields is genuinely helpful and largely fulfils the return-value burden. However, with five parameters (two undescribed) and many sibling tools, the definition leaves the agent without filter semantics or guidance on choosing this over the single-subaccount getter.

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 coverage is 60%, so id, sort, and label_selector are already documented, but name and username have no schema descriptions. The description's field list describes outputs rather than inputs and never clarifies that name/username act as filters, so it does not compensate for the coverage gap — landing just at the baseline for a partially documented schema.

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

Purpose4/5

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

The description opens with a specific verb and resource ("List subaccounts of a Storage Box") and enumerates the fields surfaced (username, home_directory, access settings, server FQDN), so the agent knows exactly what comes back. It does not explicitly contrast itself with the sibling get_storage_box_subaccount, but the list-vs-get distinction is self-evident from the verb.

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 guidance on when to use this tool rather than get_storage_box_subaccount or list_storage_boxes, and no mention of pagination, result limits, or filtering workflow. The agent must infer usage purely from the name and the returned-field list.

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