hcloud-mcp

create_rrset

Create a DNS RRSet in a Hetzner Cloud zone for records sharing one name and type, with optional TTL. Use it to add a new record set, not to update an existing one.

Instructions

Create an RRSet (all records sharing one name+type). Fails if it already exists; use add_rrset_records or set_rrset_records to change an existing one. Returns rrset + 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>",
      "records": "<records>"
    },
    "name": "create_rrset"
  }
}

Input Schema

Name	Required	Description
`ttl`	No	Omit/null = zone default
`name`	Yes	Record name relative to the zone: "@" for the apex, "www", "_acme-challenge", etc. Lowercase.
`type`	Yes
`zone`	Yes	Zone ID or name, e.g. example.com
`labels`	No
`records`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.1Nov 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, open-world behavior; the description reinforces this with the create-only failure mode and explicitly states the return shape ('Returns rrset + Action'), which matters since there is no output schema. It stops short of covering permissions, zone-existence prerequisites, or what happens to the Action object on partial failure.

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 compact sentences with the identity of the resource front-loaded, followed by failure semantics and alternatives. No filler and no restatement of the tool name.

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 6-parameter mutation tool with no output schema, it covers creation semantics, the already-exists failure, the return payload, and alternative tools. The remaining gap is the undocumented labels/comment parameters and any prerequisite that the zone must exist, which an agent must infer.

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 50%, and the description only indirectly touches parameters by defining an RRSet as name+type. Undocumented fields in the schema (type has an enum but no prose, labels has none, records.comment has none) get no compensating explanation, so it does not fully close the coverage gap.

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 an RRSet) and immediately defines the resource as 'all records sharing one name+type', which disambiguates it from record-level siblings. An agent can tell this apart from add_rrset_records or set_rrset_records without opening any schema.

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

Usage Guidelines5/5

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

Explicitly states the when-not condition ('Fails if it already exists') and names the alternatives to use instead for modification (add_rrset_records, set_rrset_records). This is direct routing rather than implied usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server