TheQRCode.io

generate_qr_code

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

TableJSON Schema

Name	Required	Description
`name`	No	Display name when saving via the authenticated API. If omitted, a name is derived from type and content.
`size`	No	Output image size in pixels (64–1024). Defaults to 256.
`type`	Yes	QR 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.
`format`	No	Output 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.
`caption`	No	Short 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.
`content`	Yes	The data to encode. Examples: 'https://example.com' for url, 'WIFI:T:WPA;S:MyNetwork;P:secret;;' for wifi, plain text for text type.
`dotStyle`	No	Shape of the QR modules. Free on every plan, keyless sessions included.
`darkColor`	No	Hex color for dark QR modules, e.g. '#1a1a1a'. Defaults to '#000000'.
`frameStyle`	No	Draw a frame around the code. 'square' means no frame. Free on every plan.
`lightColor`	No	Hex color for the background, e.g. '#ffffff'. Defaults to '#FFFFFF'.
`captionFont`	No	Typeface 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.
`cornerStyle`	No	Shape of the three large corner squares. Free on every plan.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / captionFont

Added value: +{
+  "description": "Typeface 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.",
+  "enum": [
+    "inter",
+    "oswald",
+    "bebas-neue",
+    "fredoka",
+    "playfair-display",
+    "roboto-slab",
+    "pacifico",
+    "dancing-script",
+    "permanent-marker",
+    "space-mono"
+  ],
+  "type": "string"
+}

Changed6 schema fields changedSep 20, 2026

addedInput schema / properties / caption

Added value: +{
+  "description": "Short 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.",
+  "maxLength": 60,
+  "type": "string"
+}

addedInput schema / properties / cornerStyle

Added value: +{
+  "description": "Shape of the three large corner squares. Free on every plan.",
+  "enum": [
+    "square",
+    "dot",
+    "extra-rounded"
+  ],
+  "type": "string"
+}

addedInput schema / properties / dotStyle

Added value: +{
+  "description": "Shape of the QR modules. Free on every plan, keyless sessions included.",
+  "enum": [
+    "square",
+    "dots",
+    "rounded",
+    "extra-rounded",
+    "classy",
+    "classy-rounded"
+  ],
+  "type": "string"
+}

addedInput schema / properties / format

Added value: +{
+  "description": "Output 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.",
+  "enum": [
+    "png",
+    "svg",
+    "pdf"
+  ],
+  "type": "string"
+}

addedInput schema / properties / frameStyle

Added value: +{
+  "description": "Draw a frame around the code. 'square' means no frame. Free on every plan.",
+  "enum": [
+    "square",
+    "rounded",
+    "circle",
+    "dashed"
+  ],
+  "type": "string"
+}

changedInput schema / properties / type / description

Previous value: -"QR 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. Note: 'email' requires a Bearer token — it cannot be used with the public (unauthenticated) MCP session."New value: +"QR 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."

First observedSep 10, 2026

TDQS

A4.3/5.0

Behavior5/5

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

With no annotations, the description carries the full disclosure burden and does it well: it states the return shape (hosted image URL + base64 data URL), that authentication causes the code to be saved to the user's account, that svg/pdf require a key and sit behind a per-key rate limit, and which features are free/unauthenticated. Auth requirements, side effects, and rate limiting are all surfaced.

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?

The key facts (what it does, when to use it, what it returns, auth gating) are front-loaded in the first three sentences. The later pricing-marketing sentence ('offer them freely') is somewhat promotional and bleeds into territory already covered by the schema descriptions.

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?

For a 12-parameter mutation-like tool with no annotations and no output schema, the description supplies the missing pieces: return values, authentication behavior, and feature gating. It is nearly complete, with only minor redundancy against the 100%-covered schema rather than a substantive gap.

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 every parameter's meaning, defaults, ranges and enums are already documented in the schema — including the same 'free on every plan' notes the description repeats. The description adds no per-parameter detail (e.g. format-specific constraints) beyond that, so the baseline 3 applies.

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 opens with a specific verb+resource ('Generate a QR code image') and enumerates the supported input kinds (URL, WiFi, contact, email, text). This clearly separates it from the read-only siblings get_analytics and list_qr_codes without needing their schemas.

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 an explicit trigger: 'Use this whenever a user asks to create, make, or generate a QR code for...'. That is strong when-to-use coverage, but it never names the sibling tools or states exclusions (e.g. use list_qr_codes to find an existing code), so it falls short of a 5.

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

All TheQRCode.io tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

generate_qr_code

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources