Skip to main content
Glama

Generate QR Code

qrserver.qr.generate
Read-onlyIdempotent

Generate QR code images from text or URLs. Customize size, color, background, format (PNG or SVG), and error correction level. Returns a direct image URL.

Instructions

Generate a QR code image URL from text or URL — customizable size, color, background, format (PNG/SVG), error correction level. Returns direct image URL (goqr.me)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesText or URL to encode into a QR code (required)
sizeNoImage size in WxH pixels, e.g. "200x200", "400x400" (default: "200x200")
formatNoImage format: "png" or "svg" (default: "png")
colorNoForeground color as 6-digit hex without #, e.g. "000000" for black (default: "000000")
bgcolorNoBackground color as 6-digit hex without #, e.g. "ffffff" for white (default: "ffffff")
marginNoQuiet zone margin in modules around the QR code (default: 1)
eccNoError correction level: L (7%), M (15%), Q (25%), H (30%) — higher allows more damage tolerance (default: "L")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
Behavior4/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint. Description adds that it returns a direct image URL, which is not in annotations. No contradictions. Additional behavioral context about output type is useful.

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?

Single sentence, front-loaded with key purpose, no waste. Every element earns its place.

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

Completeness5/5

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

Given output schema exists, description doesn't need to detail return structure. Mentions direct image URL and service (goqr.me). Covers all necessary aspects for a generation tool.

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% with detailed descriptions and defaults. Description lists parameters generically ('size, color, background, format, ecc') but does not add new semantic value beyond the schema.

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?

Clear verb 'Generate' and resource 'QR code image URL' are stated. Distinguishes from sibling tool 'qrserver.qr.read' by specifying generation. Mentions return of direct image URL.

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?

States when to use (encoding text/URL into QR code) and mentions customization options. Does not explicitly exclude alternatives or state when not to use, but sibling tool is for reading QR codes, so context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/whiteknightonhorse/APIbase'

If you have feedback or need assistance with the MCP directory API, please join our Discord server