Skip to main content
Glama
Sign In
hcloud-mcp

hcloud-mcp

by Xodus-CO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_zone

Create a DNS zone in Hetzner Cloud in primary or secondary mode, optionally seed records, then delegate your domain to the returned authoritative nameservers.

Instructions

Create a DNS zone. mode "primary" = Hetzner hosts the records (optionally seed with rrsets or a zonefile); "secondary" = Hetzner pulls from primary_nameservers via AXFR. Returns zone + Action. After creating, delegate the domain to the zone's authoritative_nameservers at your registrar

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": {
      "name": "<name>"
    },
    "name": "create_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttlNoDefault TTL for records without their own TTL (default 3600)
modeNoprimary
nameYesDomain name, e.g. example.com (no trailing dot)
labelsNo
rrsetsNoInitial RRSets (primary only; mutually exclusive with zonefile)
zonefileNoBIND zone file to import (primary only; mutually exclusive with rrsets)
primary_nameserversNoRequired for mode=secondary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, open-world, non-idempotent mutation, and the description adds real value beyond that: it discloses the return shape (zone + Action), the mutual exclusivity constraints, the AXFR requirement for secondary mode, and the crucial post-create step of delegating the domain to authoritative_nameservers at the registrar. It omits failure behavior such as what happens on a duplicate zone name or the fact that retries are not idempotent.

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 compact sentences, each with a distinct job: define the action, explain the mode fork, then state the return value and the follow-up delegation step. The most decision-relevant information comes first and nothing is padding.

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 7-parameter, nested-object mutation with no output schema, the description covers what it creates, the mode semantics, seeding constraints, the returned objects, and the required post-create registrar step. Only error/conflict behavior and rate or quota implications are unaddressed.

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?

Adds meaning beyond the 71%-covered schema: it explains what mode values actually cause, that rrsets/zonefile seeding applies only to primary and are mutually exclusive, and that primary_nameservers is required for secondary. Record-level value syntax is left to the schema's own descriptions, which is reasonable.

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?

States a specific verb and resource ("Create a DNS zone") and immediately disambiguates the two modes it can create, including what each mode means in terms of hosting (Hetzner hosts vs. AXFR pull). An agent knows exactly what object is produced without opening the schema.

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?

Gives clear context for choosing between mode="primary" (optionally seeded) and mode="secondary" (requires primary_nameservers via AXFR), and flags that rrsets and zonefile are mutually exclusive. It does not name sibling alternatives such as create_rrset for adding records to an existing zone, so the routing guidance stops short of explicit alternatives.

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