QR code generator. Returns a crisp SVG for text/URL payloads up to 2,048 UTF-8 bytes that fit the selected error-correction level. Paid per call: $0.003 in USDC via x402.
| Name | Required | Description | Default |
|---|---|---|---|
| ecl | No | Error correction, default M | |
| data | Yes | Payload to encode (max 2,048 UTF-8 bytes; QR capacity is lower at Q/H error correction) | |
| size | No | SVG width/height in px, default 256 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full behavioral disclosure. It details output format (SVG), payload size limits, dependency on error-correction level, and the paid-per-call cost via x402. This is comprehensive for a simple generator.
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 exactly two sentences. The first sentence states purpose, output, and constraints; the second adds cost. There is no redundant or filler content, and key information is front-loaded.
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 simple tool with a fully described schema, the description covers all necessary behavioral context: what it generates, payload limits, error-correction nuances, and cost. No output schema is needed since the output type is stated. It is complete.
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 input schema covers 100% of parameters with descriptions, so the description does not need to add parameter details. It mentions the payload limit and error-correction dependency, but these are already in the schema. Baseline 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 opens with 'QR code generator', clearly stating the tool's function and output format ('crisp SVG'). This unambiguously distinguishes it from all sibling tools (dns, sitemap, etc.), which are unrelated to QR code generation.
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 encoding text or URL payloads into QR codes, and specifies a payload limit. It does not explicitly state when not to use it, but the absence of similar siblings makes alternatives less relevant. The cost note additionally informs usage decisions.
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.
