Skip to main content
Glama
lazyants

hetzner-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Change Server Reverse DNS

hetzner_change_dns_ptr
Idempotent

Set or reset a server's reverse DNS PTR record for a public IPv4 or IPv6 address; use null to restore the default.

Instructions

Change the reverse DNS entry for one of a server's public IPv4 or IPv6 addresses. Set dns_ptr to null to reset to the default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesServer ID
ipYesPublic IPv4 or IPv6 address of the server to set the reverse DNS entry for
dns_ptrYesReverse DNS PTR record value, or null to reset to the default

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.0
    • removedInput schema / properties / dns_ptr / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / dns_ptr / type
      Added value: +[
+  "string",
+  "null"
+]
  2. First observedv2.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=true, openWorld=true and destructive=false, so the safety profile is covered. The description adds the meaningful semantic that dns_ptr=null resets to the default, but omits any auth requirements, propagation delay, or error behavior for an invalid IP address.

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?

Two tight sentences: the operation and its scope first, then the reset behavior. Nothing is wasted and the key constraint is front-loaded.

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 idempotent mutation with full schema coverage and complete annotations, the description covers the operation, scope, and reset path adequately. Only the lack of sibling routing keeps it from being fully self-sufficient.

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?

All three parameters have 100% schema description coverage, so the schema already carries the semantics and the baseline is 3. The description's null-to-reset note duplicates what the dns_ptr schema field already states, adding no new parameter information.

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 (change) and resource (reverse DNS PTR entry) scoped to a server's public IPv4/IPv6 addresses, which differentiates it from the similarly-named lb/floating-IP/primary-IP rdns siblings. It does not name those alternatives explicitly, so it stops just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives the null-reset behavior, which is useful operational guidance, but never states when to use this tool versus the parallel rdns tools (change_lb_dns_ptr, change_floating_ip_rdns, change_primary_ip_rdns). Usage is implied by the resource scope rather than stated.

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