Fetch and parse sitemap XML or gzip into JSON. For an index, follow the first N children with ?follow=N. Caps merged output at 500 URLs. Paid per call: $0.005 in USDC via x402.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public HTTP(S) sitemap URL, including .xml.gz, or a site origin to try /sitemap.xml | |
| follow | No | For a sitemap index, fetch and merge the first N children (default 0) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses key behaviors: parsing to JSON, index following via ?follow=N, the 500 URL cap, and per-call payment. It does not mention error handling or redirects, but covers the most essential operational traits.
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?
Two concise sentences deliver all key information with no filler. The core action is front-loaded, followed by specific behaviors and pricing. Every word serves a purpose.
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 tool's low complexity (2 params, no output schema, no annotations), the description covers the necessary essentials: input URL variants, follow parameter, output cap, and cost. It is complete enough for a straightforward utility.
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?
Schema coverage is 100% for both parameters, but the description adds meaningful context: it explains how the 'follow' parameter affects index handling and how the cap relates to merged output. This goes beyond the schema's basic field descriptions.
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 states 'Fetch and parse sitemap XML or gzip into JSON', specifying a distinct verb, resource, and output format. It differentiates from sibling tools which all target other domains (DNS, robots, etc.), making its purpose unambiguous.
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 gives practical guidance for handling index sitemaps ('follow the first N children') and mentions the 500 URL cap, but it does not explicitly contrast with alternative tools or state when not to use it. Context is implied rather than explicit.
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.
