Skip to main content
Glama

domain_intel

Read-only

Domain intel in one call: DNS A, AAAA, MX, NS, TXT, CNAME and CAA records, SPF and DMARC policy, plus RDAP registrar, creation and expiry dates, age in days and status codes. — $0.002 USDC per call via x402 v2 (Base or Solana).

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name, e.g. example.com (a URL is also accepted; its host is used)

Output Schema

NameRequiredDescriptionDefault
okYes
dnsNo
rdapNo
emailNo
domainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds information they do not: a per-call cost of $0.002 USDC via x402 v2 on Base or Solana, which materially affects an agent's decision to call. It stops short of covering failure modes for nonexistent or private domains.

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 sentences, front-loaded with the return payload and ending with the payment requirement. The record-type enumeration is dense but each item earns its place by telling the agent what it will receive.

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?

With an output schema present, return values need no prose explanation, and the cost model is disclosed. Gaps remain around lookup failure behavior and rate or auth constraints, which matter for an agent deciding whether to spend USDC on a call.

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?

Single parameter with 100% schema coverage, and the schema already explains that URLs are accepted with the host extracted. The description adds no further parameter meaning, so the baseline of 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?

Names the resource (domain) and enumerates exactly what is returned: DNS record types, SPF/DMARC policy, and RDAP registrar/creation/expiry/age/status. That level of specificity makes it clearly distinct from page_links and read_url, though it never explicitly states the difference.

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?

Use is implied by 'Domain intel in one call,' which signals a consolidated lookup rather than several targeted calls. There is no explicit when-to-use versus when-not guidance, no mention of alternatives, and no prerequisites.

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