Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

change_zone_ttl

Idempotent

Update a DNS zone's default TTL in seconds for all RRSets lacking their own TTL. Use it to adjust zone-wide caching through Hetzner Cloud.

Instructions

Change a zone's default TTL (applies to RRSets without their own TTL). 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>",
      "ttl": "<ttl>"
    },
    "name": "change_zone_ttl"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttlYesTTL in seconds
zoneYesZone ID or name, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, open-world mutation. The description adds the return type ("Returns an Action") and scope of effect, but does not explain whether the Action is asynchronous, what permissions are needed, or what the response contains.

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 short sentences, front-loaded with the primary action and immediately followed by the scoping clarification. Every phrase earns its place.

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 two-parameter mutation with full schema coverage and annotations, the description covers purpose, scope, and return type. The only remaining gap is that 'Action' is not explained, which would matter if the agent needs to poll or chain on the result.

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 'ttl' documented as seconds and 'zone' documented as zone ID or name. The description reinforces that this TTL is the zone default, but adds no syntax or format detail beyond the schema.

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?

The description states a specific verb and resource: "Change a zone's default TTL." It also distinguishes the scope from the sibling change_rrset_ttl by clarifying that it applies to RRSets without their own TTL, so an agent can tell the two apart.

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

Usage Guidelines4/5

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

The parenthetical establishes when this tool applies: default TTL for RRSets that do not have their own TTL. It implies per-RRSet TTL changes belong elsewhere, but does not explicitly name change_rrset_ttl as the alternative, leaving a small inference gap.

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