Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

DNS lookup

dns_lookup
Read-onlyIdempotent

Use when the user asks for the current public DNS records of a name, e.g. to confirm a change. Returns A, AAAA, CNAME, MX, NS, TXT, SOA, CAA or SRV records with TTL and the resolver that answered. No PTR (reverse DNS) lookups. Ex: 'Show the TXT records of example.com'. Free trial without an API key: a few calls a day.

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
nameYesThe DNS name to look up, e.g. _dmarc.example.com.
typesNoOptional record types, comma-separated: A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, SRV (default A).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive, so the description's job is to add operational context — and it does: it lists the returned record types with TTL and the answering resolver, and discloses a quota constraint ('Free trial without an API key: a few calls a day'). That auth/quota and return-shape detail goes well beyond what the structured fields declare.

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?

Front-loaded with the trigger phrase, then scope, then return contents, then the quota note — a sensible order with little waste. The inline example ('Show the TXT records of example.com') is mildly redundant with the usage clause, keeping it from a 5.

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 two-parameter read tool with no output schema, the description covers the trigger, the record types returned with TTL and resolver, the PTR exclusion, and the API-key/quota situation — everything an agent needs to call it and interpret the response.

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%, with both 'name' and 'types' fully documented including the allowed comma-separated values and the A default, so the schema carries the burden. The description only restates the record-type list and adds no format or edge-case guidance (e.g. how types interact with the default) beyond what is already structured.

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 ('current public DNS records of a name') and enumerates exactly which record types come back (A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, SRV). It also scopes itself out against reverse lookups ('No PTR'), so an agent can separate it from specialized siblings like mx, caa, or dmarc.

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?

Gives a clear triggering condition ('when the user asks for the current public DNS records of a name, e.g. to confirm a change') plus an explicit exclusion (no PTR/reverse DNS). It stops short of naming when to prefer a sibling such as mx, caa, or nameservers, leaving that routing to inference.

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.