Domain registration data (modern WHOIS) via RDAP: registrar, created/expiry dates, status, nameservers, DNSSEC. Paid per call: $0.005 in USDC via x402.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain to look up (path parameter) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since no annotations are provided, the description carries the full burden. It discloses the paid per-call cost ($0.005 in USDC via x402) and the returned data categories, which are critical behavioral traits. It does not mention error conditions or rate limits, but for a read-only lookup tool, the key behaviors are addressed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficiently structured sentence with two parts: the tool's purpose and its pricing. It front-loads the main function and includes only essential additional information (cost), with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple input schema and absence of an output schema, the description supplies the necessary return-value context by listing the data fields (registrar, dates, status, nameservers, DNSSEC) and the cost. It does not explain the output format or potential errors, but these are minor gaps for a straightforward lookup tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter 'domain' is fully described in the schema as 'Domain to look up (path parameter)', providing 100% coverage. The description adds no additional parameter-specific context beyond what the schema already states, 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.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the tool as providing domain registration data via RDAP, with a specific list of data fields (registrar, created/expiry dates, status, nameservers, DNSSEC). This distinguishes it from sibling tools like dns or lei, which serve different domain-related lookups.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for fetching registration data, and 'modern WHOIS' signals its role relative to traditional tools. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to select it when registration data is needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool addresses a distinct function: DNS resolution, email authentication, web extraction, legal entity lookup, QR generation, RDAP lookup, robots.txt parsing, sitemap parsing, text cleaning, and VAT calculation. There is no overlap or ambiguity between them.
All tool names are lowercase, concise, and use hyphens for compound words. Although some are nouns and some verbs, the style is uniform and each name clearly indicates its purpose, following a predictable convention.
With exactly 10 tools, the set is well-scoped for a general web utility server. Each tool covers a distinct need, and the count falls comfortably within the optimal 3-15 range.
The tools cover a comprehensive range of DNS, WHOIS, and domain-related functions, including DNS lookup, RDAP registration data, email auth, robots.txt, and sitemaps. The additional utilities (extract, text-clean, QR, LEI, VAT) round out the server without leaving obvious gaps in its stated purpose.
