QR Branding

Generate a QR code (manual)

qr_generate

Read-onlyIdempotent

Generate a fully branded QR code with explicit control over colors, module/finder shapes, logo, caption, and output format. Use this when the user already knows the design they want.

Input Schema

Name	Required	Description
`text`	No	Optional caption rendered below the QR (e.g. a slogan).
`content`	Yes	The text or URL the QR will encode. Required.
`logoUrl`	No	Public HTTPS URL of a logo image to embed at the center.
`eccLevel`	No	Error-correction level (L=7%, M=15%, Q=25%, H=30%). Higher levels survive more damage but are denser.
`frameText`	No	Label inside the frame, max 40 characters, any language (e.g. "Scan me", "View the menu"). Defaults to "Scan me".
`fileFormat`	No	Output format. Defaults to "png".
`frameColor`	No	Frame colour in hex, also the label background. Defaults to "#000000".
`frameStyle`	No	Call-to-action frame around the whole QR with a short label. Never covers the QR or its quiet zone.
`moduleShape`	No	Shape of the small modules in the QR matrix.
`outputWidth`	No	Output width in pixels (raster) or viewport units (svg). 64-4096.
`outputHeight`	No	Output height in pixels (raster) or viewport units (svg). 64-4096.
`primaryColor`	No	Foreground/module color in hex (e.g. "#000000" or "#0a84ff").
`frameTextColor`	No	Frame label colour in hex. Defaults to "#FFFFFF".
`backgroundColor`	No	Background color in hex (e.g. "#ffffff"). Use "transparent" for no background.
`additionalConfig`	No	Escape hatch: any other QrConfig field the engine accepts (gradient stops, dot rotation, etc.). Merged on top of the structured fields above.
`finderInnerShape`	No	Shape of the inner dot of the three corner finder patterns.
`finderOuterShape`	No	Shape of the outer ring of the three corner finder patterns.

Output Schema

Name	Required	Description
`format`	Yes	File format the engine rendered: png, svg, jpg, webp or pdf.
`content`	No	The text or URL the QR encodes, when the call set it.
`filePath`	No	PDF in the stdio package only: local temp file the PDF was written to.
`mimeType`	No	MIME type of the rendered file (the engine's contentType).
`sizeBytes`	No	Size of the rendered file in bytes, as reported by the engine.
`resourceUri`	No	PDF on the remote server only: URI of the embedded resource block that carries the file.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 19, 2026

changedInput schema / properties / additionalConfig / description

Previous value: -"Escape hatch: any other QrConfig field the engine accepts (gradient stops, dot rotation, frame text, etc.). Merged on top of the structured fields above."New value: +"Escape hatch: any other QrConfig field the engine accepts (gradient stops, dot rotation, etc.). Merged on top of the structured fields above."

addedInput schema / properties / frameColor

Added value: +{
+  "description": "Frame colour in hex, also the label background. Defaults to \"#000000\".",
+  "type": "string"
+}

removedInput schema / properties / frameShape

Removed value: -{
-  "description": "Decorative frame around the QR.",
-  "enum": [
-    "none",
-    "banner",
-    "balloon",
-    "ribbon",
-    "rounded-rect",
-    "rect"
-  ],
-  "type": "string"
-}

addedInput schema / properties / frameStyle

Added value: +{
+  "description": "Call-to-action frame around the whole QR with a short label. Never covers the QR or its quiet zone.",
+  "enum": [
+    "none",
+    "banner-bottom",
+    "banner-top",
+    "rounded-box",
+    "speech-bubble",
+    "ticket"
+  ],
+  "type": "string"
+}

addedInput schema / properties / frameText

Added value: +{
+  "description": "Label inside the frame, max 40 characters, any language (e.g. \"Scan me\", \"View the menu\"). Defaults to \"Scan me\".",
+  "maxLength": 40,
+  "type": "string"
+}

addedInput schema / properties / frameTextColor

Added value: +{
+  "description": "Frame label colour in hex. Defaults to \"#FFFFFF\".",
+  "type": "string"
+}

Changed1 schema field changedOct 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "content": {
+      "description": "The text or URL the QR encodes, when the call set it.",
+      "type": "string"
+    },
+    "filePath": {
+      "description": "PDF in the stdio package only: local temp file the PDF was written to.",
+      "type": "string"
+    },
+    "format": {
+      "description": "File format the engine rendered: png, svg, jpg, webp or pdf.",
+      "type": "string"
+    },
+    "mimeType": {
+      "description": "MIME type of the rendered file (the engine's contentType).",
+      "type": "string"
+    },
+    "resourceUri": {
+      "description": "PDF on the remote server only: URI of the embedded resource block that carries the file.",
+      "type": "string"
+    },
+    "sizeBytes": {
+      "description": "Size of the rendered file in bytes, as reported by the engine.",
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "format"
+  ],
+  "type": "object"
+}

First observedOct 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds that this path gives the agent explicit design control, which is useful vs the AI sibling, but says nothing extra about auth, rate limits, or side effects beyond what annotations provide.

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 tight sentences: the capability and its scope come first, and the routing condition follows immediately. Every sentence earns its place with no filler or restated title.

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 17 parameters, a nested escape-hatch object, and an output schema, the description does not need to explain return values or enumerate parameters. It is nearly complete, but a brief explicit contrast with the AI/template siblings would make the routing decision fully self-contained.

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 (including enums, hex colors, dimensions, and the additionalConfig escape hatch) is already documented in the schema. The description only groups those parameters into categories and adds no syntax, defaults, or format nuance beyond the schema, so baseline 3 applies.

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 states a specific verb+resource ("Generate a fully branded QR code") and enumerates the controllable dimensions (colors, module/finder shapes, logo, caption, output format). It aligns with the "manual" title, but it never names the AI or template siblings it differs from, so differentiation is implied rather than explicit.

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?

"Use this when the user already knows the design they want" gives a clear selection condition and implicitly excludes the AI/template paths for users who don't. It stops short of naming qr_generate_ai or qr_generate_from_template as the alternatives, leaving the routing inference to the agent.

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

All QR Branding tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?