Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

change_dns_ptr

Idempotent

Set or reset reverse DNS (PTR) records for a Hetzner Cloud server, Primary IP, Floating IP, or load balancer by providing a hostname or null.

Instructions

Set or reset reverse DNS (PTR) for a public IP of a server, Primary IP, Floating IP, or load balancer. dns_ptr is always required: pass a hostname to set it, or null to reset it to the Hetzner default. Returns an Action

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resource": "<resource>",
      "id": "<id>",
      "ip": "<ip>",
      "dns_ptr": "<dns_ptr>"
    },
    "name": "change_dns_ptr"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID of the server / Primary IP / Floating IP / load balancer
ipYesThe public IP to set the PTR for (IPv4, or a single IPv6 address within the resource's /64)
dns_ptrYesHostname, e.g. mail.example.com; null resets to default
resourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds meaningfully beyond that: the null-reset semantic (a mutation that changes behavior depending on input) and the fact that it returns an Action, which tells the agent this is an asynchronous operation.

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?

Three short sentences: scope, the one non-obvious input rule, and the return type. Nothing is repeated and the most decision-relevant information comes first.

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 four-parameter, all-required mutation with no output schema, the description covers scope, the nullable-parameter rule, and the Action return. It stops short of noting any permission requirements or what an error looks like, which would be the final useful addition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%, with the resource enum having no description in the schema; the description compensates by spelling out the four resource kinds and by reinforcing that dns_ptr is mandatory and nullable. The IPv4/IPv6 /64 detail is left to the schema, which documents it adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

State a specific verb pair ("set or reset") and a specific resource (reverse DNS / PTR), and enumerates the four resource kinds it applies to (server, Primary IP, Floating IP, load balancer). This clearly distinguishes it from the other change_* siblings, which mutate unrelated attributes.

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 makes the set-vs-reset decision concrete by stating dns_ptr is always required and that null restores the Hetzner default, which is real usage guidance. It does not, however, state any preconditions, when to prefer this tool over a zone-record tool, or what happens on failure, so guidance is implied rather than explicit.

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