Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

change_rrset_ttl

Idempotent

Sets a DNS RRSet's TTL to a chosen number of seconds or null to fall back to the zone default, letting you control DNS caching duration for records in a Hetzner Cloud zone.

Instructions

Change an RRSet's TTL. ttl is required: a number of seconds, or null to fall back to the zone 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": {
      "zone": "<zone>",
      "name": "<name>",
      "type": "<type>",
      "ttl": "<ttl>"
    },
    "name": "change_rrset_ttl"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttlYesTTL in seconds
nameYesRecord name relative to the zone: "@" for the apex, "www", "_acme-challenge", etc. Lowercase.
typeYes
zoneYesZone ID or name, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the write nature, idempotency, and non-destructiveness, so the description's main addition is the null-ttl fallback to the zone default and the Action return. It omits preconditions such as whether the RRSet must already exist and what happens on a missing record.

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, front-loaded with the operation and then the one non-obvious argument semantic. Nothing is redundant or padded.

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 four-parameter mutation with no output schema and no annotations gap, the essentials are present, but the absence of precondition and error behavior leaves an agent without enough to predict failure modes.

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% and the schema explains zone and name, but it leaves the null branch of the ttl anyOf unexplained. The description fills that gap by clarifying that null means fall back to the zone default, which is genuinely additive meaning.

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?

"Change an RRSet's TTL" gives a specific verb and resource, and the RRSet scoping implicitly separates it from zone-level siblings like change_zone_ttl. It stops short of naming an alternative explicitly, so an agent must infer the boundary.

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 explicit guidance on when to use this versus change_zone_ttl, update_rrset, or set_rrset_records. The only conditional present is about the ttl value itself (seconds or null), not about tool selection.

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