Skip to main content
Glama
Sign In
zwznco

TheQRCode

by zwznco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

generate_qr_code

Create QR code images for URLs, WiFi networks, contacts, email, or text, returning a hosted image URL and inline base64 data URL.

Instructions

Generate a QR code image. Use this whenever a user asks to create, make, or generate a QR code for a URL, website, WiFi network, contact card, email, or text. Returns a hosted image URL and a base64 data URL for inline display. Colour, size, dot and corner styling, frames and captions are free on every plan and with no key at all — offer them freely. When authenticated, the QR code is saved to the user's account and svg/pdf output becomes available.

Input Schema

NameRequiredDescriptionDefault
nameNoDisplay name when saving via the authenticated API. If omitted, a name is derived from type and content.
sizeNoOutput image size in pixels (64–1024). Defaults to 256.
typeYesQR code type. Use 'url' for web links, 'wifi' for network credentials (format: WIFI:T:WPA;S:<ssid>;P:<password>;;), 'contact' for vCard data, 'text' for arbitrary strings, 'email' for email addresses. Every type works without a key.
formatNoOutput format, returned as a data URL of that type. Defaults to 'png'. svg and pdf REQUIRE an API key: vector and PDF are the most expensive render path, so they sit behind a per-key rate limit rather than a per-IP one. This is a cost control, not a plan feature — both are free in the dashboard and in the browser generator on every plan.
captionNoShort text rendered under the code, e.g. 'Scan for the menu'. Forces a frame to be drawn, because the text needs a band to sit on. Free on every plan.
contentYesThe data to encode. Examples: 'https://example.com' for url, 'WIFI:T:WPA;S:MyNetwork;P:secret;;' for wifi, plain text for text type.
dotStyleNoShape of the QR modules. Free on every plan, keyless sessions included.
darkColorNoHex color for dark QR modules, e.g. '#1a1a1a'. Defaults to '#000000'.
frameStyleNoDraw a frame around the code. 'square' means no frame. Free on every plan.
lightColorNoHex color for the background, e.g. '#ffffff'. Defaults to '#FFFFFF'.
captionFontNoTypeface for the caption. Defaults to 'inter' (bold sans). 'pacifico' and 'dancing-script' are scripts, 'permanent-marker' is handwritten, 'playfair-display' and 'roboto-slab' are serifs. Ignored without a caption.
cornerStyleNoShape of the three large corner squares. Free on every plan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.2

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so richly: it discloses the return values (hosted image URL plus base64 data URL), the authentication effect (saving to the account, enabling svg/pdf), and a critical cost-control caveat that svg/pdf are rate-limited per-key rather than a plan restriction. That is exactly the kind of behavior an agent needs before calling.

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

Conciseness4/5

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

It is front-loaded with purpose, then return values, then free-feature guidance, then auth-gated behavior. Every sentence is informative, though it leans heavily on repeated 'free on every plan' emphasis that could be trimmed slightly without loss of meaning.

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 12 parameters but 100% schema coverage, no output schema, and no annotations, the description supplies the missing behavioral context (return format, auth behavior, rate-limit caveat). It is nearly complete, but does not mention validation or error behavior for bad payloads.

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 description coverage is 100%, so the baseline is 3; the schema already documents all 12 parameters, defaults, formats, and constraints in detail. The description adds the useful free/auth distinction for output formats and styling, but does not explain parameter syntax 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?

States a specific verb and resource ('Generate a QR code image') and enumerates the supported payload kinds (URL, WiFi, contact card, email, text). It is clearly distinguishable from siblings list_qr_codes and get_analytics, which manage/a… and analyze existing codes rather than produce one.

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 explicitly triggers on user intent ('whenever a user asks to create, make, or generate a QR code'), which is actionable guidance. It does not name the sibling tools or state when not to use this one (e.g. to list or analyze existing codes), so it falls short of 5.

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

Deploy Server

Other Tools