Generate QR codes for URLs, WiFi, contacts and text. Paid API key adds saved codes + analytics.
Scored across 1 tool
With only a single tool, there is no ambiguity between tools. The tool's purpose is clear and well defined for generating QR codes.
The tool name uses a clear verb_noun structure (generate_qr_code), which is consistent within the server. Since there is only one tool, consistency is trivially maintained, but the name is appropriately descriptive.
A single tool for generating QR codes feels extremely thin. While the tool covers multiple QR types (URL, WiFi, contact, email), it lacks any supporting tools like list, delete, or customization options, making the server feel underdeveloped for typical use cases.
The server provides only the generate operation, which is a one-way action. There are no tools to list previously generated QR codes, delete them, or edit them, even though the description mentions saving to the user's account, implying a need for management tools.
Generate a QR code image. Use this whenever a user asks to create, make, or generate a QR code for a URL, website, WiFi network, contact card, email, or text. Returns a hosted image URL and a base64 PNG data URL for inline display. When authenticated, the QR code is saved to the user's account.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Display name when saving via the authenticated API. If omitted, a name is derived from type and content. | |
| size | No | Output image size in pixels (64–1024). Defaults to 256. | |
| type | Yes | QR code type. Use 'url' for web links, 'wifi' for network credentials (format: WIFI:T:WPA;S:<ssid>;P:<password>;;), 'contact' for vCard data, 'text' for arbitrary strings, 'email' for email addresses. Note: 'email' requires a Bearer token — it cannot be used with the public (unauthenticated) MCP session. | |
| content | Yes | The data to encode. Examples: 'https://example.com' for url, 'WIFI:T:WPA;S:MyNetwork;P:secret;;' for wifi, plain text for text type. | |
| darkColor | No | Hex color for dark QR modules, e.g. '#1a1a1a'. Defaults to '#000000'. | |
| lightColor | No | Hex color for the background, e.g. '#ffffff'. Defaults to '#FFFFFF'. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states that it returns a hosted image URL and a base64 PNG data URL, and explains that when authenticated, the QR code is saved to the user's account. It also notes the Bearer token requirement for 'email' type inside the schema, which is transparent. It doesn't mention potential errors or rate limits, but the behavior it does disclose is relevant and sufficient for a typical QR generation tool.
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 concise and well-structured. It opens with a direct statement of purpose and use cases, then follows with output details and a note on authentication. Every sentence contributes to understanding, and the information is front-loaded. There is no fluff or repetition.
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?
The tool has no output schema, so the description compensates by stating the return format (hosted image URL and base64 data URL). It also covers the key behavioral aspects, such as saving when authenticated and the token requirement. For a tool with six parameters and no siblings, all necessary context is present, making it 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?
Schema description coverage is 100%, but the description adds value beyond the schema. It explains the type enum with concrete examples for each type (e.g., wifi format), clarifies defaults for size and colors, and notes the authentication requirement for email. This complements the schema without redundancy, providing meaningful context for correct parameter usage.
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 the tool's purpose: generating a QR code image. It lists the specific content types it supports (URL, WiFi, contact, email, text) and explains the output format. Since there are no sibling tools, the purpose is unambiguous and distinct.
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 provides explicit guidance on when to use the tool ('whenever a user asks to create, make, or generate a QR code'), which is a clear usage trigger. It also mentions the authentication context for saving, though it doesn't discuss alternatives since none exist. This is clear context, but lacks explicit exclusions or comparison to other tools, so a 4 is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
generate_qr_codeFree styled QR code generator API. Create QR codes with custom colors, logos, and frame templates. Supports URL, WiFi, Email, Phone, SMS. No API keys required.
Generate QR codes for URLs, PIX, Wi-Fi, vCards, WhatsApp and more. For AI agents.
Generate static QR codes (URL, WiFi, vCard, pixel art) and decode QR images. Codes never expire.
Generate QR codes and create, edit and track dynamic (editable) QR codes with scan analytics, over a hosted MCP server plus a free REST API. Free, no watermark, no expiry. Every tool takes a free API key from https://openqr.uk/api.
