x402 agent toolkit: service finder, payment safety, Solana & web tools

by dev.workers.moneytools.x402-pay-precheck

Domain registration (RDAP)

domain_rdap

Read-onlyIdempotent

Registrar, creation/expiry dates, age in days, status codes, nameservers and DNSSEC from RDAP; flags very new domains (phishing signal) and near expiry. Free: 10 calls/day; then $0.002/call via x402 (MCP params._meta["x402/payment"] or HTTP) or X-API-Key credits. [served by tools.moneytools.dev]

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_rdap"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	domain name

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds valuable context beyond those annotations: a daily free limit, per-call cost, x402 and API-key payment paths, and special flags for new or near-expiry domains. It does not contradict 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the returned data fields and special flags, then compresses operational and payment details into a second sentence. The semicolon-heavy enumeration is dense, but every part carries relevant information and nothing is 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?

An output schema and annotations cover the return shape and safety profile, while the description supplies data fields, special flags, rate limits, and payment paths. Complete for a one-parameter lookup tool; the lack of error behavior is minor given the output schema.

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?

The single domain parameter is fully documented in the schema with 100% coverage and an example. The description does not add format constraints, validation rules, or other meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 the tool retrieves RDAP domain registration data and enumerates returned fields including registrar, dates, status, nameservers, and DNSSEC, plus flags new and near-expiry domains. It does not explicitly name a sibling alternative, but the resource and scope are unmistakable.

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?

Provides an implied use case through phishing detection for very new domains and expiry monitoring, but does not state when to choose this over alternatives or any exclusions. The pricing and payment notes are operational rather than usage-selection guidance.

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

All x402 agent toolkit: service finder, payment safety, Solana & web tools 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.

Resources

Need Help?