Skip to main content
Glama

Get DNS records

get_dns
Read-onlyIdempotent

Nameservers and DNS records (A/AAAA/CNAME/MX/TXT) of a domain you own.

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": "get_dns"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds useful scope: it names the exact record types returned and implies an ownership/authorization constraint ('a domain you own'). It does not say what happens when the domain has no records, whether both nameservers and records are always returned together, or anything about the response shape.

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?

One short, front-loaded sentence with no filler; the record-type list is the highest-value information and comes first. It is a noun phrase rather than a statement of action, which slightly weakens readability but costs no words.

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?

For a simple single-parameter read tool with rich annotations and no output schema, the description covers what is returned and roughly who can call it. It leaves gaps around what a nameserver lookup versus a record lookup yields, empty/error results, and the domain argument format, which matter for a DNS tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single 'domain' parameter, so the description must carry the load. 'A domain you own' partially compensates by implying an ownership/registration requirement, but it gives no format (apex vs subdomain, IDN, TLD inclusion) that would let an agent build a correct argument.

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 resource (nameservers and DNS records) and enumerates the record types returned (A/AAAA/CNAME/MX/TXT), which lets an agent distinguish it from set_dns or apply_dns_template. It stops short of a clear verb (the retrieval is only implied by the title), so it is clear but one step from ideal.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives such as whois_lookup or dns_email_check, which an agent could easily confuse with this tool. Only the phrase 'of a domain you own' hints at a prerequisite, and even that is left implicit.

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