Skip to main content
Glama
mjmirza

hetzner-mcp

by mjmirza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

cloud_list_locations

List Hetzner Cloud locations for deployment planning. Filter by ID or attributes to find the right region, with read-only access.

Instructions

List locations. Read only.

Input Schema

TableJSON 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.1/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 burden, and it does disclose the key trait: 'Read only.' That is a genuine safety signal for an agent deciding whether the call mutates state. However, nothing is said about pagination, result size, or what a 'location' contains, which are the remaining behaviors an agent would want.

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?

Two terse sentences, front-loaded with the action and followed by the safety trait; nothing is wasted. It is efficient but borders on under-specification rather than true conciseness.

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 tool with a nested-object filter, an optional verbose flag, and no output schema, the description is too thin: it never explains what a location represents, what verbose changes, or how the query filter behaves. An agent could call it, but not confidently.

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 each of the three parameters is documented inline, so the schema does the heavy lifting and a 3 baseline applies. The description adds no parameter meaning beyond the schema and never mentions the id-based single-fetch path.

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 names a specific verb and resource ('List locations'), which is unambiguous and distinct from every sibling, none of which touch locations. It stops short of 5 because it offers no scope detail (filtering, pagination, region) that would let an agent anticipate behavior.

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 or when-not-to-use guidance, and no alternative is named. The agent must infer that this is the tool to call whenever location data is needed; the 'id' parameter's single-fetch mode is never mentioned as a usage branch.

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