Skip to main content
Glama

Add DNS record

add_dns_record

Add a DNS record to a domain's zone on Sitequest's nameservers. It is added next to existing records of the same name and type, never replacing one: check list_dns_records first to avoid duplicates, use edit_dns_record to change a value and delete_dns_record to remove one. Only served while the domain uses Sitequest's nameservers (see get_domain). No CNAME at the apex or beside other records of the same name; one SPF TXT record per name. Resolvers see the change within minutes; a replaced record can be cached up to its old TTL.

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": {
      "id": "<id>",
      "type": "<type>",
      "name": "<name>",
      "ttl": "<ttl>",
      "data": "<data>"
    },
    "name": "add_dns_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe domain ID
ttlYesTime to live in seconds, at least 60. 3600 is usual; use 300 before a planned change
dataYesRecord value: an IPv4 address for A, IPv6 for AAAA, a hostname for CNAME, ALIAS and NS, the text for TXT
nameYesRecord name relative to the domain: '@' for the domain itself, 'www' for www.<domain>, '_dmarc' for _dmarc.<domain>
typeYesDNS record type

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations (which only say readOnly=false, destructive=false): it discloses that records are added alongside same-name/type records and never replace them, that CNAME at apex or beside same-name records is disallowed, one SPF TXT per name, and real-world propagation/caching timing. This is exactly the operational context an agent needs before writing DNS.

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?

Four dense sentences, front-loaded with the action, then dedup guidance, then constraints, then propagation timing. No filler and nothing repeated from the title or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter mutation tool with no output schema, it covers prerequisites, sibling routing, record-type constraints, and post-write effects. An agent can invoke it correctly without consulting other documentation.

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 coverage is 100% and already documents id, name, type, ttl and data including examples. The description adds only indirect parameter meaning via validation constraints (no apex CNAME, one SPF TXT) and the TTL caching note; it does not further explain field formats, so baseline 3 is appropriate.

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 ('Add a DNS record to a domain's zone') and scopes it to Sitequest's nameservers. It is immediately distinguishable from edit_dns_record, delete_dns_record and list_dns_records, which are named directly.

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?

Gives explicit when-to-use routing: check list_dns_records first to avoid duplicates, use edit_dns_record to change a value, delete_dns_record to remove one, and get_domain to confirm nameserver delegation. Prerequisites and alternatives are both covered.

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.