Generate a custom QR code in PNG or SVG format.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 4.2/5 across 1 of 1 tools scored.
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.
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.
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.
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.
generate_qr_codeAInspectGenerate 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).
| 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). |
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.
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.
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.
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.
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.
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.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
