Genexxis paid agent tools (x402)

domainaudit_whois_bulk

RDAP registration data for up to 10 domains in one call (registrar, created, updated, expires, days left, status, nameservers, DNSSEC), looked up in parallel. Price: $0.02 USDC per call, paid with x402 on Base.

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": {
      "domains": "<domains>"
    },
    "name": "domainaudit_whois_bulk"
  }
}

Input Schema

Name	Required	Description	Default
`domains`	Yes	Comma-separated domains, max 10

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses parallel lookup, the 10-domain cap, and the $0.02 USDC x402 payment on Base. It does not mention read-only semantics or partial-failure behavior, but the cost and batching model are clear.

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 tight sentences front-load the resource and batch limit, then list returned fields and pricing. Every clause adds useful information without waste.

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?

For a one-parameter lookup with no output schema, the description gives enough context to call it: returned fields, batch limit, parallel behavior, and payment method. Minor gaps remain around sibling routing and partial-failure handling.

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 parameter, domains, has 100% schema description coverage specifying comma-separated domains with max 10. The description repeats the max-10 limit but adds no format details beyond the schema, so 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?

Names RDAP registration data, bulk up to 10 domains, and enumerates returned fields, making the resource and batch scope clear. It does not explicitly contrast with domainaudit_domain_info, the likely single-domain sibling, so it falls 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 Guidelines3/5

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

The phrase 'up to 10 domains in one call' and the bulk framing imply batch usage, and the price signals a paid lookup. However, there is no explicit when-to-use/when-not guidance or reference to the single-domain alternative.

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

All Genexxis paid agent tools (x402) 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?