Agent Margin Router

Domain RDAP

domain_rdap

Read-only

Domain registration data via RDAP (the WHOIS successor): registered flag, registrar, status, registration/expiry events, nameservers and DNSSEC – for availability checks and due diligence. Pay per call with USDC or USDT on Base via x402. 3 free calls per wallet.

Input Schema

TableJSON Schema

Name	Required	Description
`domain`	Yes	Registrable domain, e.g. example.com.
`wallet`	No	Your EVM wallet address (0x...). Unlocks the free tier (3 free calls per wallet).
`api_key`	No	Optional AMR enterprise API key.
`x_payment`	No	Optional signed x402 payment payload (base64 JSON) for USDC/USDT on Base.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`token`	No	Token actually used for payment (USDC, USDT or FREE).	USDC
`domain`	Yes
`events`	No
`source`	Yes
`status`	No
`routing`	Yes	How the request was routed (provider, fallback, cache, latency).
`rdap_url`	No
`cost_usdc`	Yes	Price charged in stablecoin units (USDC/USDT 1:1); 0 on the free tier.
`registrar`	No
`fetched_at`	No	UTC timestamp when the data was fetched.
`registered`	Yes
`nameservers`	No
`dnssec_signed`	No
`freshness_seconds`	Yes	Age of the underlying data in seconds (0 = fetched live).
`registrar_iana_id`	No
`x_payment_response`	No	Base64-encoded x402 settlement receipt (mirrors the X-PAYMENT-RESPONSE header). Only present when the call was paid with `x_payment`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Response for ``POST /domain-rdap``.",
+  "properties": {
+    "cost_usdc": {
+      "description": "Price charged in stablecoin units (USDC/USDT 1:1); 0 on the free tier.",
+      "title": "Cost Usdc",
+      "type": "number"
+    },
+    "dnssec_signed": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Dnssec Signed"
+    },
+    "domain": {
+      "title": "Domain",
+      "type": "string"
+    },
+    "events": {
+      "additionalProperties": true,
+      "title": "Events",
+      "type": "object"
+    },
+    "fetched_at": {
+      "description": "UTC timestamp when the data was fetched.",
+      "format": "date-time",
+      "title": "Fetched At",
+      "type": "string"
+    },
+    "freshness_seconds": {
+      "description": "Age of the underlying data in seconds (0 = fetched live).",
+      "title": "Freshness Seconds",
+      "type": "integer"
+    },
+    "nameservers": {
+      "items": {
+        "type": "string"
+      },
+      "title": "Nameservers",
+      "type": "array"
+    },
+    "note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Note"
+    },
+    "rdap_url": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Rdap Url"
+    },
+    "registered": {
+      "title": "Registered",
+      "type": "boolean"
+    },
+    "registrar": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Registrar"
+    },
+    "registrar_iana_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Registrar Iana Id"
+    },
+    "routing": {
+      "description": "How the request was routed (provider, fallback, cache, latency).",
+      "properties": {
+        "cache_hit": {
+          "default": false,
+          "description": "True if the result was served from cache.",
+          "title": "Cache Hit",
+          "type": "boolean"
+        },
+        "fallback_used": {
+          "default": false,
+          "description": "True if the primary provider failed and a fallback served the result.",
+          "title": "Fallback Used",
+          "type": "boolean"
+        },
+        "latency_ms": {
+          "default": 0,
+          "description": "End-to-end routing latency in milliseconds.",
+          "title": "Latency Ms",
+          "type": "integer"
+        },
+        "provider": {
+          "description": "Name of the upstream provider that served the result.",
+          "title": "Provider",
+          "type": "string"
+        },
+        "providers_tried": {
+          "description": "Providers attempted, in order.",
+          "items": {
+            "type": "string"
+          },
+          "title": "Providers Tried",
+          "type": "array"
+        }
+      },
+      "required": [
+        "provider"
+      ],
+      "title": "RoutingMeta",
+      "type": "object"
+    },
+    "source": {
+      "title": "Source",
+      "type": "string"
+    },
+    "status": {
+      "items": {
+        "type": "string"
+      },
+      "title": "Status",
+      "type": "array"
+    },
+    "token": {
+      "default": "USDC",
+      "description": "Token actually used for payment (USDC, USDT or FREE).",
+      "title": "Token",
+      "type": "string"
+    },
+    "x_payment_response": {
+      "description": "Base64-encoded x402 settlement receipt (mirrors the X-PAYMENT-RESPONSE header). Only present when the call was paid with `x_payment`.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "freshness_seconds",
+    "cost_usdc",
+    "routing",
+    "domain",
+    "registered",
+    "source"
+  ],
+  "type": "object"
+}

AddedSep 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already mark the tool as read-only and open-world; the description adds useful operational context: it is a paid API (USDC/USDT on Base via x402) with 3 free calls per wallet. No behavioral contradictions with the annotations.

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 concise sentences: the first front-loads the data categories and use cases, and the second covers payment and free-tier mechanics. Every sentence earns its place with no redundancy.

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?

For a single-required-parameter read-only lookup with a full output schema and complete schema coverage, the description covers purpose, use case, data fields, and payment/free-tier behavior. Nothing essential is missing.

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 all parameters are already documented in the schema. The description adds no per-parameter semantics beyond what the schema provides, 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?

The description identifies the resource ('domain registration data') and the method ('via RDAP') and lists concrete fields such as registrar, status, nameservers, and DNSSEC. It is clear about what the tool does, but it does not explicitly distinguish it from sibling tools like dns_whois.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states clear use cases ('for availability checks and due diligence') and gives payment/free-tier conditions, giving an agent enough context to decide when to use it. It does not explicitly say when not to use it or which alternative to prefer.

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

All Agent Margin Router tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.