Skip to main content
Glama
mjmirza

hetzner-mcp

by mjmirza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

storagebox raw request

storagebox_request

Send requests to any Hetzner Storage Box API endpoint using a relative path. Reads are free; writes follow read-only and cost guards.

Instructions

Call any Hetzner Storage Box (api.hetzner.com) endpoint directly. Use a relative path like /servers. Reads are free. Writes obey the read-only and cost guards. If an endpoint you need is missing or misbehaving, use the contribute_or_report tool to open a prefilled issue or pull request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoRequest body for write methods, as a JSON object, for example {"name":"web1","type":"spread"}. A JSON string is also accepted and parsed.
pathYesRelative API path, for example /servers or /servers/123.
queryNoQuery string parameters.
methodNoHTTP method. Defaults to GET.
confirmNoMust be true to create a billed resource. Reads and free resources do not need it.
verboseNoReturn the full payload. Default false returns a compact, token-efficient view.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.0
    • removedInput schema / properties / query / additionalProperties / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  }
-]
    • addedInput schema / properties / query / additionalProperties / type
      Added value: +[
+  "string",
+  "number",
+  "boolean"
+]
  2. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that reads are free, that writes are gated by read-only and cost guards, and that a prefilled issue/PR route exists. It does not describe auth requirements, rate limits, or error behavior for failed writes.

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?

Four short sentences, front-loaded with the core action, then constraints, then the escape hatch. No filler, though the cost-guard and contribute_or_report sentences could be tightened slightly.

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 generic passthrough with no output schema, the description covers the essential call semantics and safety guards. It leaves return formatting/pagination and error-shape behavior unstated, but the verbose flag partially covers response shape.

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 body/path/query/method/confirm/verbose are all already documented with examples. The description adds no parameter syntax or format information beyond the schema, so the baseline 3 applies.

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 and resource: call any Hetzner Storage Box endpoint directly with a relative path. It is clearly the raw/escape-hatch tool distinct from the typed siblings like storagebox_list, though it never explicitly contrasts itself with them.

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?

Gives concrete usage context ('Use a relative path like /servers') and an explicit escalation rule naming the alternative: 'If an endpoint you need is missing or misbehaving, use the contribute_or_report tool.' It does not say when to prefer storagebox_list/storagebox_list_types over this generic path.

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