Skip to main content
Glama
TLDMint MCP Server
by cputop

inspect_domain_dns_whois

Check any domain’s live DNS records and WHOIS registration/expiration data to verify configuration and ownership status.

Instructions

Inspect live DNS propagation (A, AAAA, www CNAME, MX, SPF, DMARC, NS via Cloudflare 1.1.1.1 DoH) and ICANN RDAP WHOIS registration/expiration dates for any domain.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name to inspect (e.g. "tldmint.com").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does valuable work by naming the upstream sources (Cloudflare 1.1.1.1 DoH, ICANN RDAP), which tells the agent results are external/authoritative and implicitly read-only, but it never states the operation is non-mutating, says nothing about rate limits, timeouts, or how a domain with no records differs from one that does not resolve.

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?

A single front-loaded sentence with zero filler; the parenthetical record list is dense but every item conveys what the agent will observe, so nothing is wasteful.

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 one-parameter tool with no output schema, the description is nearly complete: it enumerates the record types and the WHOIS date fields the caller can expect. The remaining gap is that it never sketches the response shape (per-record values, missing-record behavior) or error conditions for an unregistered domain.

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 coverage is 100% and there is only one required parameter, so the schema already fully documents the input. The description adds only marginal meaning ("any domain"), which is adequate for this baseline.

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?

A specific verb ("Inspect") applied to two clearly named resources (live DNS records and RDAP WHOIS registration/expiration data), with the exact record types and upstream resolvers listed. This is unmistakable against siblings like check_domain_availability or get_verified_domain_coupons, which cover availability and pricing rather than live records.

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 implied by "live DNS propagation" and "any domain" — the agent can infer this is the tool for current DNS/registration state. But there is no explicit when-to-use framing, no note on when to prefer a sibling, and no prerequisite (e.g. does it require a registered domain, does it work for unregistered ones?).

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