Skip to main content
Glama
Sign In
hetzner-mcp

hetzner-mcp

by mjmirza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

cloud_list_volumes

List Hetzner Cloud volumes to view storage details, filter by name or label selector, or fetch a specific volume by ID.

Instructions

List volumes. Read only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cloud_list_volumes"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoFetch one by id.
queryNoFilters, e.g. name, label_selector.
verboseNoFull payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.7.0
    • changedInput schema / properties / id / description
      Previous value: -"Optional resource id to fetch a single item."New value: +"Fetch one by id."
    • 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"
+]
    • changedInput schema / properties / query / description
      Previous value: -"Optional query parameters such as name or label_selector."New value: +"Filters, e.g. name, label_selector."
    • changedInput schema / properties / verbose / description
      Previous value: -"Return full payload instead of the compact view."New value: +"Full payload."
  2. First observedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully states "Read only," confirming this is a safe read operation, but it does not disclose auth needs, rate limits, pagination, or return format, leaving significant gaps.

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?

The description is two short, front-loaded sentences with no wasted words. Both "List volumes" and "Read only" earn their place by conveying purpose and a key behavioral trait.

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 simple read-only list tool with full schema coverage and no output schema, the description is minimally adequate. However, it lacks any usage context around filtering, fetching by id, or verbose behavior, so an agent gets only a partial picture.

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 the schema documents id, query, and verbose. The description adds no parameter meaning, so the baseline 3 is appropriate 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?

The description gives a specific verb and resource, "List volumes," which clearly identifies the operation. It does not differentiate from sibling list tools or describe scope/filtering, but the name and phrase make the purpose clear.

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 alternatives such as cloud_create_volume or cloud_delete_volume, and no prerequisites or filtering context. "Read only" describes behavior rather than usage.

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