Skip to main content
Glama

domfacts__rdap

RDAP registration facts: registrar, created and expiry dates, domain age, days to expiry, nameservers, EPP status. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/domfacts/rdap

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / domain / description
      Added value: +"Domain name, e.g. example.com"
    • addedInput schema / required
      Added value: +[
      +  "domain"
      +]
  2. First observed

TDQS

B3.4/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 genuinely useful behavior: a $0.01 per-call cost, USDC on Base (eip155:8453), the x402 payment object location in params._meta, and the underlying HTTP GET endpoint. It says nothing about what happens when payment is absent, error/not-found behavior for unregistered domains, or rate limits, leaving notable gaps for an unannotated tool.

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?

Two dense sentences, both fully load-bearing: the first front-loads the return payload, the second front-loads cost and payment mechanics plus the transport. Nothing is repeated from the schema or wasted.

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?

With no output schema, listing the returned fields is the right compensatory move, and the payment/cost model is fully spelled out. What remains missing is edge-case behavior (unregistered or invalid domains, payment failure) which matters for a paid endpoint.

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?

Only one parameter exists and schema description coverage is 100% (the schema already documents 'domain' with an example). The description adds no format constraints, TLD restrictions, or IDN handling beyond what the schema states, so the baseline 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?

The description names the resource precisely (RDAP registration facts) and enumerates exactly what is returned: registrar, created/expiry dates, domain age, days to expiry, nameservers, EPP status. That enumeration implicitly separates it from siblings like domfacts__dns (DNS records) or domfacts__monitor, but no sibling is named explicitly, so it stops short of a 5.

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 when-to-use or when-not-to-use guidance, and no routing to alternatives such as domfacts__dns, domain_intel__lookup, or company_facts__domain. An agent must infer from the returned-field list alone whether this is the right tool versus those siblings.

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