Skip to main content
Glama
lazyants

hetzner-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Storage Box Subaccounts

hetzner_list_storage_box_subaccounts
Read-onlyIdempotent

List subaccounts of a Hetzner Storage Box, with optional filters by name, username, or labels. Use it to audit or manage access for a specific Storage Box.

Instructions

List the subaccounts of a Storage Box, with optional filtering by name, username, or labels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesStorage Box ID
nameNoFilter by name
sortNoSort field, e.g. "id:asc" or "name:desc"; pass an array for multiple sort fields
usernameNoFilter by subaccount username
label_selectorNoLabel filter, e.g. "env=prod,tier=web"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.0.0
    • addedInput schema / properties / sort / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / sort / description
      Previous value: -"Sort field, e.g. \"id:asc\" or \"name:desc\""New value: +"Sort field, e.g. \"id:asc\" or \"name:desc\"; pass an array for multiple sort fields"
    • removedInput schema / properties / sort / type
      Removed value: -"string"
  2. Addedv2.3.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, covering the safety profile. The description adds only that filtering is optional; it does not disclose auth needs, rate limits, pagination, or return format. With annotations carrying the behavioral burden, this is a modest addition.

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?

One front-loaded sentence with no filler. It efficiently states purpose and filtering, though it could be slightly more complete by mentioning sort.

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 read-only list tool with full annotation coverage and complete parameter documentation in the schema, the description states the operation and optional filters adequately. The only notable gap is usage routing against the singular get sibling, which belongs to usage guidelines.

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 100%, so all five parameters (id, name, sort, username, label_selector) are already documented in the schema. The description lists name, username, and labels as filters but omits sort and the required id; baseline 3 applies 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.

Purpose4/5

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

States a specific verb ('List') and resource ('subaccounts of a Storage Box') with filtering scope. Clear enough to distinguish from the singular get_storage_box_subaccount sibling, but does not explicitly name the alternative or rule it out.

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?

No when-to-use guidance. It does not say when to call this versus hetzner_get_storage_box_subaccount or other list endpoints, nor any prerequisites. Usage is only implied by the tool name.

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