Skip to main content
Glama
benswel

QR for Agent

create_qr_code

Create a customizable QR code that redirects to a URL and can be updated later without regenerating the image. Supports colors, dot/corner styles, logos, gradients, frames, expiry, scheduled URL switching, and GTM tracking.

Instructions

Create a new managed QR code with optional custom styling. The QR code points to a short URL that redirects to your target URL. You can change the target URL later without regenerating the QR image. Supports custom colors, dot shapes, corner shapes, and logo embedding.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
target_urlYesThe destination URL the QR code should redirect to.
labelNoAn optional label to identify this QR code.
formatNoImage format. "svg" is recommended (smaller, scalable, text-parseable). Use "png" only if a bitmap is required.svg
foreground_colorNoHex color for QR code dots. Default: #000000 (black).
background_colorNoHex color for QR code background. Default: #ffffff (white).
widthNoQR code width in pixels. Default: 400.
marginNoQuiet zone margin in modules. Default: 2.
error_correctionNoError correction level. L=7%, M=15% (default), Q=25%, H=30%. Auto-set to H when logo is provided.
dot_styleNoShape of data modules. square=classic, rounded=soft corners, dots=circles, classy-rounded=organic.
corner_styleNoShape of finder patterns (corner squares). square=classic, extra-rounded=smooth, dot=circular.
logo_urlNoURL to a logo image (PNG/JPG/SVG) or data:base64 URI. Centered on the QR code.
logo_sizeNoLogo size as ratio of QR width (0.15-0.3). Default: 0.2.
gradientNoApply a gradient to QR dots and corners instead of solid foreground_color.
frame_styleNoDecorative frame around QR. 'banner_bottom': text below, 'banner_top': text above, 'rounded': rounded border with text.
frame_textNoCTA text on the frame (e.g. 'Scan Me!', 'View Menu'). Max 30 chars. Requires frame_style.
frame_colorNoHex color for frame background. Default: #000000.
frame_text_colorNoHex color for frame text. Default: #ffffff.
frame_border_radiusNoFrame corner radius. Only for 'rounded' style.
expires_atNoISO 8601 date-time. After this date, scanning returns 410 Gone instead of redirecting.
scheduled_urlNoReplacement URL that activates at scheduled_at.
scheduled_atNoISO 8601 date-time when target automatically switches to scheduled_url.
gtm_container_idNoGoogle Tag Manager container ID (e.g. 'GTM-ABC123'). Enables GTM tracking on QR scans via an intermediate HTML page.
Behavior3/5

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

Without annotations, the description discloses that the QR code uses a short URL redirect and that target can be updated. It notes auto-set error correction with logo. However, it omits potential costs, auth requirements, or rate limits. Sufficient for a creation tool but could be more transparent about side effects.

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 a single paragraph of four sentences, no wasted words. It front-loads the main action, then adds key benefits and customization options. Ideal length for a tool with many parameters.

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 22 parameters including nested objects and no output schema, the description provides a solid overview of capabilities and benefits. It could be more complete by noting what the response contains (e.g., QR code image data or ID), but the description covers the main use case sufficiently.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value beyond schema by explaining the managed nature (pointing to short URL, changeable target) and summarizing key customization options. This extra information helps the agent understand behavior not evident from individual parameter descriptions.

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 the tool creates a managed QR code with optional custom styling. It distinguishes from specialized sibling QR creators (e.g., create_email_qr, create_wifi_qr) by being a general-purpose tool for targeting a URL that can be changed later.

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 highlights the key benefit of being a managed QR code with changeable target URL, implying it is best when future updates are needed. It does not explicitly contrast with specialized QR creators, but the generic nature is evident. Lacks explicit when-not-to-use guidance.

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/benswel/qr-agent-core'

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