Skip to main content
Glama
Sign In
OnlyDNS MCP Server

OnlyDNS MCP Server

Official
by Onlydns
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

add_record

Add DNS records to a domain and append new values to existing record sets; accepts relative hostnames, qualified names, or FQDNs for automatic canonicalization.

Instructions

Add a DNS record to a domain. Accepts relative hostnames (e.g. "testing"), domain-qualified names (e.g. "testing.example.com"), or canonical FQDNs (e.g. "testing.example.com."). If a record with the same name and type already exists, the new value is appended to the record set.

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": {
      "domainName": "<domainName>",
      "name": "<name>",
      "type": "<type>",
      "value": "<value>"
    },
    "name": "add_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttlNoTime to live in seconds (default: 300)
nameYesRecord name/subdomain. Accepts relative name (e.g. "testing", "www", "@"), domain-qualified name (e.g. "testing.example.com"), or full canonical FQDN (e.g. "testing.example.com."). Canonicalization is handled automatically.
typeYesDNS record type (e.g. A, AAAA, CNAME, MX, TXT, SRV, CAA, NS, URL, PROXY)
valueYesRecord content/value (e.g. "1.2.3.4", "v=spf1 include:... ~all", "10 mail.example.com"). Can be a single string or array of strings.
domainNameYesDomain name (e.g. example.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.5
    • changedInput schema / properties / name / description
      Previous value: -"Record name/subdomain (e.g. \"@\", \"www\", \"mail\", or \"app.example.com\")"New value: +"Record name/subdomain. Accepts relative name (e.g. \"testing\", \"www\", \"@\"), domain-qualified name (e.g. \"testing.example.com\"), or full canonical FQDN (e.g. \"testing.example.com.\"). Canonicalization is handled automatically."
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden. It usefully discloses duplicate handling (new value appended to the record set) and accepted hostname forms, but it omits permissions, reversibility, propagation timing, and return behavior for a mutation operation.

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?

The description is two tight sentences. The core purpose is front-loaded, followed by accepted input formats and duplicate behavior, with no wasted text.

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

Completeness3/5

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

The core invocation is covered, including hostname formats and duplicate append behavior. But with no annotations and no output schema, the description remains incomplete about authorization, side effects, and what the caller receives after adding a record.

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%, so all five parameters are already documented. The description repeats the accepted name formats but does not add meaningful parameter semantics beyond the schema; baseline 3 applies.

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?

The description states a specific verb and resource: "Add a DNS record to a domain." It also clarifies duplicate name/type behavior, which helps distinguish it from update_record and set_records, though it does not explicitly name those alternatives.

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

Usage Guidelines3/5

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

Usage is implied by "Add" and by the note that an existing same-name/type record will have the new value appended. However, the description gives no explicit when-to-use guidance, prerequisites, or named alternatives for replacing versus appending records.

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