Skip to main content
Glama

DNS lookup

dns_lookup

Look up a hostname via Cloudflare DNS (A, AAAA, CNAME, MX, TXT, NS, CAA, SOA). type email_auth returns MX, SPF, DMARC, and the DNSSEC AD flag. Does not connect to the name.

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

Input Schema

NameRequiredDescriptionDefault
nameYesHostname. No scheme or path.
typeNoA, AAAA, CNAME, MX, TXT, NS, CAA, SOA, or email_auth. Default A.

Output Schema

NameRequiredDescriptionDefault
okNo
nameNo
typeNo
rcodeNo
answersNo
dnssec_adNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 disclosure burden and does reasonably well: it names the upstream resolver (Cloudflare), discloses the composite behavior of email_auth (returns MX, SPF, DMARC plus DNSSEC AD flag), and clarifies that no connection is made to the target. It is silent on error behavior for nonexistent domains and on rate limits, which keeps it from a 5.

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?

Three short sentences, front-loaded with the core action and record-type coverage, followed by the special mode and the scoping caveat. Every clause adds information; nothing is redundant with the name or title.

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?

An output schema exists, so return-value structure need not be described. The description covers provider, accepted types, the special composite mode, and the no-connection caveat, which is enough for an agent to call it correctly. Error/NXDOMAIN handling is the main untold piece given there are no annotations.

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%, so the schema itself documents both parameters and the baseline is 3. The description does add one piece of genuine meaning beyond the schema: it explains what the email_auth value actually returns, which the schema merely lists as an option without elaboration. That is useful but limited to a single enum value.

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?

The description opens with a specific verb and resource ("Look up a hostname via Cloudflare DNS") and enumerates exactly which record types are covered, including the special email_auth mode. The closing clause "Does not connect to the name" cleanly separates it from HTTP-fetching siblings like check_url and fetch_page.

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?

It gives clear context for the email_auth mode (use it to gather MX, SPF, DMARC, and the DNSSEC AD flag in one call) and establishes a boundary by stating the tool does not connect to the hostname, routing HTTP checks elsewhere. It stops short of explicitly naming an alternative tool or stating hard when-not conditions.

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