Skip to main content
Glama

Domain Intel - RDAP WHOIS, DNS records, SSL certificate

domain_intel
Read-onlyIdempotent

One call for a domain: RDAP registration (registrar, created, expires, status, nameservers, DNSSEC) from the official IANA RDAP servers, live DNS (A, AAAA, MX, NS, TXT, CAA, SPF, DMARC) and the TLS certificate (issuer, expiry, days left, SANs). Free: 25 calls/day per IP. Paid: $0.005 per call via x402 at https://radarbg.com/x402/domain-intel.

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": "github.com"
    },
    "name": "domain_intel"
  }
}

Input Schema

NameRequiredDescriptionDefault
tlsNoAlso check the TLS certificate on port 443
domainYesDomain name, e.g. example.com

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 declare readOnlyHint, idempotentHint, and openWorldHint, yet the description adds genuinely useful behavior beyond them: data provenance (official IANA RDAP servers), a concrete rate limit of 25 calls/day per IP, and a paid fallback at $0.005 per call via x402 with an endpoint URL. It does not cover failure modes (NXDOMAIN, RDAP rate-limiting, partial DNS failures) or whether results are cached, which keeps it below 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 sentences, front-loaded with the scope statement and then the commercial terms; every listed item (registrar, DNSSEC, DMARC, SANs) is substantive. The first sentence is a long parenthetical run-on that could be broken up, but no wording is filler.

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 return values and does so field by field for all three data sources, plus provenance, rate limits, and paid access. For a two-parameter read-only lookup, an agent has everything it needs to call it correctly and interpret the result.

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, and the baseline of 3 applies. The description does clarify what the tls flag yields (issuer, expiry, days left, SANs) and enumerates the DNS record types, but it never states what tls=false actually skips or saves, so it adds only marginal meaning over the schema.

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?

States a concrete verb-and-resource ("One call for a domain") and enumerates exactly what is retrieved: RDAP registration fields, live DNS record types, and TLS certificate attributes. It is far more specific than a title restatement, but it never distinguishes itself from siblings such as domain_security_report, email_auth, or website_report, which an agent could plausibly pick for overlapping needs.

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 context is implied by the listed data sources and the free-tier/paid pricing model, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. The agent must infer that this is the broad domain-lookup tool rather than, say, the security-focused or email-auth-focused sibling.

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