Skip to main content
Glama

BRAINIAC Email & Domain Intelligence

Look up domain registration

email-domain_registration-lookup

Read public RDAP data for the domain, including registrar, registration and expiration events, status, and nameservers. A not-found response is not proof the domain is unregistered everywhere. Price $0.05 USDC. POST /api/v1/email-domain/registration-lookup. Unpaid calls return 402 and do not run.

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": "email-domain_registration-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: a $0.05 USDC cost, that unpaid calls return 402 and do not execute, and that a not-found result is inconclusive. That is above-average billing/failure disclosure, but it omits other traits an agent needs, such as latency, caching/freshness of the registry data, or whether repeated calls are re-billed.

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?

Front-loaded with purpose, followed by the caveat and then the billing/endpoint facts, so an agent gets the essentials first. The raw 'POST /api/v1/email-domain/registration-lookup' path is mostly implementation detail that costs a sentence without aiding selection.

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?

No output schema and no annotations exist, so the description must cover both semantics and returns, and it does summarize the returned fields reasonably well while flagging the paid-call failure mode. It falls short only on input format details and on freshness/repeat-call behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it only refers to 'the domain' without specifying accepted form (bare registered domain vs. URL vs. subdomain) or IDN handling, despite maxLength 253 hinting at hostname input. No meaning is added beyond the single documented property.

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?

States a specific verb and resource ('Read public RDAP data for the domain') and enumerates the returned content: registrar, registration and expiration events, status, and nameservers. That content set cleanly separates it from the DNS-record siblings (mx-record-check, spf-record-analyze, dkim-record-check), so an agent can pick it without opening the schema.

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 by the resource ('registration lookup'), and the sibling list of DNS/validation checks establishes context but is never referenced. The one piece of genuine guidance is interpretive rather than selective: 'A not-found response is not proof the domain is unregistered everywhere.' No explicit when-to-use, when-not-to-use, or alternative routing is given.

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