EZ QR Generator

generate_qr_code

Generate custom QR codes. Free Tier: Basic URL/Text PNG. Paid Tier ($0.001 USD via x402): Vector SVG, custom styling (dotStyle, primaryColor, logoUrl), or premium QR types (wifi, vcard, crypto, dbl).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	No	The URL or text to encode in the QR code. Optional if using other tab types.
`format`	No	Output format. 'png' is free. 'svg' vector output requires x402 micropayment ($0.001).	png
`dblCode`	No	Dragon Ball Legends code. Required if activeTab is 'dbl'. Requires x402 micropayment ($0.001).
`logoUrl`	No	Image URL or base64 data URL to embed in the center of the QR code. Requires x402 micropayment ($0.001).
`dotStyle`	No	Visual style of QR dots. 'square' is free. Custom styles ('circle', 'hex', 'diamond') require x402 micropayment ($0.001).	square
`eccLevel`	No		H
`activeTab`	No	QR payload type. Free: 'url', 'text'. Paid via x402: 'wifi', 'vcard', 'email', 'phone', 'sms', 'whatsapp', 'facebook', 'instagram', 'twitter', 'youtube', 'tiktok', 'linktree', 'location', 'paypal', 'dbl', 'crypto', 'spotify', 'linkedin', 'telegram', 'github', 'discord', 'twitch'.	url
`primaryColor`	No	Hex color code, e.g. '#00f0ff'. Custom colors require x402 micropayment ($0.001).

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of disclosure. It clearly reveals the x402 micropayment requirement for premium features, which is a crucial behavioral trait. It does not cover failure modes or error handling, but the core cost implication is transparently stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences long, front-loaded with the primary purpose, and efficiently conveys the free/paid split. Every word earns its place, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of 8 parameters and no output schema, the description does a good job of summarizing the core free/paid options. However, it omits the 'json' output format present in the schema and does not mention the optionality or activeTab-driven payload types. Nonetheless, the schema covers most details, so the description is reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 88%, so the input schema already documents almost all parameters. The description mentions dotStyle, primaryColor, and logoUrl as custom styling, but these details are already in the schema descriptions. No added semantic meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Generate custom QR codes' with a specific verb and resource. It distinguishes free vs paid tiers, which further clarifies the tool's scope. With no sibling tools to confuse, this is a strong purpose statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit context for when to use free vs paid features (Free Tier: Basic URL/Text PNG; Paid Tier: $0.001 via x402). It does not state exclusions or alternatives, but there are no sibling tools, so the guidance is sufficient for selecting the right options.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All EZ QR Generator tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The tool's name and description clearly indicate its purpose of generating QR codes.

Naming Consistency5/5

The single tool uses a clear verb_noun convention (generate_qr_code), which is descriptive and consistent. There are no other names to create inconsistencies.

Tool Count4/5

The server has a focused purpose and one tool fully covers it. While one tool is on the low end of the typical range, it is reasonable for a simple QR generator and does not feel excessive or inadequate.

Completeness5/5

The tool supports basic and premium QR generation, custom styling, and multiple QR types, covering the full scope of the domain. There are no obvious missing operations that would impede a user's workflow.

Resources

Need Help?