Skip to main content
Glama

Whoisxml Dns

whoisxml_dns
Read-onlyIdempotent

DNS records for , A, AAAA, MX, NS, TXT, and other records with their values and TTLs. Example: whoisxml_dns({ domain: "google.com", _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "google.com",
      "_apiKey": "your-whoisxml-api-key"
    },
    "name": "whoisxml_dns"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name to resolve DNS records for, e.g. "google.com"
_apiKeyYesWhoisXML API key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds that response records carry values and TTLs, which is useful since no output schema exists, but says nothing about resolution failures, missing records, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The first sentence is front-loaded and efficient, but the example call duplicates the schema's existing examples array almost verbatim, including a placeholder API key. That sentence consumes space without adding information the agent doesn't already have.

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 two-parameter read tool with full annotation and schema coverage, the description is adequate on purpose and return content. It is incomplete only on when-to-use routing and edge-case behavior, which are the remaining gaps an agent might need.

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%, with both domain and _apiKey documented, so the baseline is 3. The description only restates the domain concept and reproduces an example already present in the schema's examples field, adding no new parameter meaning.

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?

Names the specific resource (DNS records) and enumerates concrete record types (A, AAAA, MX, NS, TXT) plus returned values and TTLs, which clearly separates it from the whois and reverse-whois siblings. No explicit verb, but 'records for <domain>' is unambiguous enough for an agent to select it.

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 guidance on when to use this versus whoisxml_whois, whoisxml_reverse_whois, or whoisxml_whois_history, and no stated prerequisites beyond the obvious API key. The agent must infer selection from the tool name alone.

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.