Skip to main content
Glama

DomainVet

DNS lookup (A, AAAA, MX, NS, TXT, CAA, SOA...)

dns_lookup
Read-onlyIdempotent

Resolve DNS records for a domain via DNS-over-HTTPS (1.1.1.1): A, AAAA, MX, NS, TXT (SPF/verification), CNAME, CAA, SOA, SRV, HTTPS, DS, DNSKEY. Returns values with TTLs, whether the domain exists (NXDOMAIN) and whether the answer was DNSSEC-validated.

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
typesNoComma-separated record types (default A,AAAA,MX,NS,TXT,CNAME,CAA,SOA). Also SRV,HTTPS,DS,DNSKEY,PTR
domainYesDomain or hostname

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly, openWorld and idempotent, yet the description adds real value beyond them: the transport (DNS-over-HTTPS via 1.1.1.1) and the shape of the answer, including TTLs, NXDOMAIN existence signalling and DNSSEC validation status. It omits failure modes such as timeouts or rate limits, which keeps it off 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with the operation and its resolver front-loaded, and return behaviour second. The type enumeration is partly duplicated between description and schema, which is the only inefficiency.

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?

With no output schema, the description carries the burden of describing returns, and it does so precisely (TTLs, NXDOMAIN, DNSSEC status). For a two-parameter read-only lookup, an agent has everything needed 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 description coverage is 100%, so both parameters are already documented, including the default type set and the extra types. The description restates the type list and adds no new format or syntax guidance, so the 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 ('Resolve DNS records for a domain') and enumerates the supported record types, which clearly separates it from siblings like rdap_domain or ssl_certs. It never names an alternative, so it lands at a clear 4 rather than a 5.

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 only implied: the parenthetical '(SPF/verification)' hints at TXT-record use cases, but there is no explicit when-to-use, when-not-to-use, or routing to a sibling such as rdap_domain for registration data.

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