Skip to main content
Glama

Set DNS records / nameservers

set_dns
DestructiveIdempotent

Set DNS records and/or nameservers of a domain you own. records: [{type: A|AAAA|CNAME|MX|TXT|NS (SRV/CAA/ALIAS not supported on hosted DNS: use custom nameservers), name: '@'|sub, value, ttl?, priority? (MX)}]. mode 'replace' (default) replaces the FULL record set; mode 'merge' adds/updates the given records, deletes any in remove [{type,name,value?}], and keeps everything else (safer for adding MX/TXT next to a website).

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

Input Schema

NameRequiredDescriptionDefault
modeNo
domainYes
removeNo
recordsNo
nameserversNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / records / items / properties / type / enum
      Previous value: -[
      -  "A",
      -  "AAAA",
      -  "CNAME",
      -  "MX",
      -  "TXT"
      -]New value: +[
      +  "A",
      +  "AAAA",
      +  "CNAME",
      +  "MX",
      +  "TXT",
      +  "NS"
      +]
    • changedInput schema / properties / remove / items / properties / type / enum
      Previous value: -[
      -  "A",
      -  "AAAA",
      -  "CNAME",
      -  "MX",
      -  "TXT"
      -]New value: +[
      +  "A",
      +  "AAAA",
      +  "CNAME",
      +  "MX",
      +  "TXT",
      +  "NS"
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / mode
      Added value: +{
      +  "enum": [
      +    "replace",
      +    "merge"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / remove
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "name": {
      +        "type": "string"
      +      },
      +      "type": {
      +        "enum": [
      +          "A",
      +          "AAAA",
      +          "CNAME",
      +          "MX",
      +          "TXT"
      +        ],
      +        "type": "string"
      +      },
      +      "value": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "type",
      +      "name"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description earns its place by disclosing the exact blast radius: 'replace' replaces the FULL record set, whereas 'merge' deletes only what is listed in remove and 'keeps everything else'. That is the single most important behavioral fact for an agent choosing a mode, and it is not derivable from the annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then dense but purposeful detail on mode semantics and record shape; no filler sentences. The bracketed inline schema notation is efficient but slightly hard to parse on a first read, and the SRV/CAA caveat is buried mid-parenthetical.

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 destructive, five-parameter mutation with no output schema and zero schema coverage, the description covers the dangerous parts well: what replace destroys, what merge preserves, and which record types are unsupported. It stops short of propagation timing, whether nameservers and records can be set in the same call, or what the response reports, which an agent may still need to set expectations.

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?

With 0% schema description coverage the description carries the load, and it does most of it: it documents the records object shape (type/name/value/ttl/priority), the '@' root-name convention, MX-only priority, the supported type enum, and the remove object shape. The nameservers parameter is only mentioned in the opening clause with no format guidance (how many, ordering, whether it replaces existing NS), which is the main remaining gap.

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?

States a specific verb and resource — 'Set DNS records and/or nameservers of a domain you own' — with the ownership precondition and the record-type scope made explicit. It reads clearly against read-only siblings like get_dns, but it never names apply_dns_template, the other write path for DNS, so the sibling boundary is left implicit.

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 solid conditional guidance for the mode parameter: 'replace' is the default and rewrites the full set, while 'merge' is called out as 'safer for adding MX/TXT next to a website', which tells an agent when to prefer each. It also routes unsupported record types (SRV/CAA/ALIAS) toward custom nameservers, but offers no guidance on when to use this tool versus apply_dns_template or whether to call get_dns first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources