Skip to main content
Glama

dns_lookup

Resolve DNS records for a domain to get A, AAAA, MX, NS, TXT, CNAME, SOA, CAA, SRV or ANY answers with structured and raw output; handles NXDOMAIN and missing records without failure.

Instructions

Resolve DNS records for a domain (A, AAAA, MX, NS, TXT, CNAME, SOA, CAA, SRV or ANY).

Returns structured answers plus the raw text form. Handles NXDOMAIN and missing records without failing. Use ANY for a full passive DNS profile.

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

Input Schema

NameRequiredDescriptionDefault
domainYes
record_typeNoA

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses the return shape (structured answers plus raw text form) and, importantly, that NXDOMAIN and missing records are handled without failing — a non-obvious error behavior an agent needs. It omits rate limits, timeout behavior, and whether ANY may be refused by some resolvers.

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 short lines, front-loaded with the verb and resource, then return shape, then error behavior, then the ANY tip. 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 two-parameter read-only lookup with no annotations and no output schema, the description covers purpose, valid inputs, return form, and failure semantics. Only minor gaps remain (domain format expectations, timeouts, resolver choice), which are unlikely to cause a wrong call.

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?

Schema description coverage is 0% and there are no enums, so the description's enumeration of valid record_type values (A, AAAA, MX, NS, TXT, CNAME, SOA, CAA, SRV, ANY) is the only source of that constraint and directly compensates for the schema gap. The domain parameter's expected format (bare hostname vs URL) is still unspecified.

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 opens with a specific verb and resource ('Resolve DNS records for a domain') and enumerates exactly which record types can be fetched, so an agent knows precisely what the tool produces. It stops short of naming a sibling to contrast with (e.g. reverse_dns or dns_resolver_compare), so differentiation is left to inference.

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?

'Use ANY for a full passive DNS profile' is a genuine when-to-use hint, but it addresses only parameter selection. There is no guidance on when to prefer this over reverse_dns or dns_resolver_compare, nor on prerequisites such as whether the domain must be bare (no scheme, no www).

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