Fetch and parse robots.txt (+ llms.txt if present) into structured JSON, including which AI crawlers are blocked. Paid per call: $0.005 in USDC via x402.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public HTTP(S) site origin or URL |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the transparency burden. It reveals pricing and payment method ($0.005 in USDC via x402), and mentions that llms.txt is conditionally parsed ('if present'), giving insight into behavioral variation. However, it does not discuss error handling or missing robots.txt scenarios.
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?
One sentence plus pricing information, front-loaded with the core action. Every word contributes to clarity, with no redundant phrases.
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?
For a tool with one parameter and no output schema, the description covers the primary functionality, output type, and pricing. It is reasonably complete, though it could briefly mention failure behavior (e.g., if robots.txt is not found), but this is not a major gap.
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 the single 'url' parameter, so the description doesn't need to add much parameter detail. The description repeats 'URL' without adding new meaning beyond the schema's 'Public HTTP(S) site origin or URL'.
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 a specific verb ('Fetch and parse') and resource ('robots.txt (+ llms.txt if present)'), and the output is structured JSON. It also differentiates from sibling tools like 'sitemap' by focusing on robots.txt and AI crawler blocking.
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 usage for checking robots.txt and AI crawler permissions, but it does not explicitly state when to use this tool versus alternatives (e.g., sitemap for sitemaps). No when-not-to-use guidance is provided.
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.
