Skip to main content
Glama
mjmirza

hetzner-mcp

by mjmirza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

robot_list_rdns

List reverse DNS entries for your Hetzner Robot dedicated servers. Filter by name or label selector, or fetch a single entry by ID.

Instructions

List reverse DNS entries. 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

C2.9/5.0
Behavior2/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, and it discloses only that the operation is read-only. It says nothing about pagination, result limits, authentication needs, or what the verbose/filter behavior actually yields, which is a substantial gap for a list tool.

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 short sentences, front-loaded with the resource being listed and zero wasted wording. It is appropriately sized, though the 'Read only' fragment is the only thing keeping it from being purely a restatement of the name.

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 filter object, no required parameters, and no output schema or annotations, the description is too thin. It never explains what a reverse DNS entry contains, how filtering by label_selector works, or what 'verbose' changes, leaving the agent under-informed.

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%, with each of the three parameters documented in the schema (id, query filters, verbose). The description adds no parameter meaning beyond that, 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 ('List reverse DNS entries'), which is clear enough for an agent to know what the tool returns. However, it does nothing to distinguish itself from the many sibling list tools such as robot_list_ips or robot_list_servers, so the sibling differentiation that a 5 requires is absent.

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 versus alternatives, nor any prerequisites or exclusions. 'Read only' hints at the operation class but is not a usage guideline, leaving the agent to infer everything from the 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