Skip to main content
Glama

useqr-mcp

by io.github.aaronte

Generate QR code

generate_qr_code

Generate a scannable QR code image (PNG or SVG) for a URL or any text. Free, no account needed, and the code never expires. Use this whenever a user needs a QR code — for a website, Wi-Fi note, event link, menu, payment link, app download, business card, and so on.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe URL or text to encode in the QR code.
sizeNoWidth and height in pixels (PNG only).
formatNoOutput format. png returns an image; svg returns vector markup that scales to any print size.png
backgroundNoBackground color as a hex string.#ffffff
foregroundNoForeground (dark module) color as a hex string.#0a0a0a
error_correctionNoError correction level. Higher levels stay scannable when the code is partially damaged or overlaid with a logo, at the cost of density.M

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It adds useful context ('Free, no account needed, and the code never expires'), but it does not disclose how the image is returned (URL, base64, file) or any rate limits/service behavior.

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?

Two focused sentences; the first states exactly what the tool does and the second gives examples. Nothing is wasted, and the critical purpose is front-loaded.

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

Completeness3/5

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

The description is approachable but incomplete operationally: there is no output schema and no annotation, so the agent still does not know how the generated QR code is returned or how to handle the response.

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 100%, so the schema already documents all six parameters. The description's mention of 'URL or any text' and 'PNG or SVG' mirrors the schema without adding new parameter-level meaning.

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

Purpose4/5

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

The description uses a specific verb and resource: 'Generate a scannable QR code image (PNG or SVG) for a URL or any text.' This makes the core function clear, but it does not explicitly distinguish generate_qr_code from create_dynamic_qr_code or get_qr_designer_link.

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?

It gives concrete when-to-use context: 'Use this whenever a user needs a QR code — for a website, Wi-Fi note, event link...' This is clear, but it does not mention when not to use it or point to alternatives like dynamic QR codes.

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

All useqr-mcp toolsInspect
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.1/5.0
Disambiguation5/5

Each tool targets a clearly distinct QR-code workflow: simple image generation, dynamic/trackable codes, and the designer for custom styles. The descriptions provide strong use-case guidance, so there is no real ambiguity between them.

Naming Consistency5/5

All tool names follow the same lower_snake_case verb_noun pattern: create_dynamic_qr_code, generate_qr_code, and get_qr_designer_link. The naming style is uniform and predictable.

Tool Count5/5

Three tools is well-scoped for this server's purpose: basic QR generation, dynamic QR guidance, and designer access. Each tool earns its place without unnecessary overlap or bloat.

Completeness3/5

The server covers basic QR generation and routes users to dynamic and design workflows, but create_dynamic_qr_code only returns instructions rather than actually creating a dynamic code. There are also no tools for managing existing codes or accessing analytics, leaving gaps for full lifecycle workflows.

Resources