Skip to main content
Glama

Design a QR code

design_qr
Read-onlyIdempotent

Design a QR code for any content type (link, Wi-Fi, contact, email, SMS, WhatsApp, payments, social profiles and more) with the style you choose: colors and gradients, dot, eye and eye center shapes, a built-in call-to-action frame with its text or a custom frame spec, a border, a logo icon or your own uploaded logo (logo_file_id, with an API key), margin and error correction. Can start from a built-in preset or a community item. Validates the content like the QRdx editor, checks the scan score with the editor's scan check and repairs the style until it is Great (at most 3 repairs, then a classic black-on-white code). Returns the score, what was changed and why, the style JSON (qrdxStyle, ready for save_template and generate_qr_code), a playground_url that opens the design in the QRdx editor, a PNG and the SVG. Call list_options first for the accepted values.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "content": "<content>"
    },
    "name": "design_qr"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoWidth of the code in pixels (128-1024); frames add to it
styleNoHow the code looks. Leave options out for defaults (or the preset's or community item's): eyes and eye centers follow the dot color, square shapes, margin 4, level Q, no frame.
presetNoStart from a built-in QRdx theme by id (list_options lists them); style options you set win over it
contentYesWhat the code opens: a type and its fields (list_options lists the fields of every type)
include_svgNoReturn the SVG markup (often 50-150 KB)
logo_file_idNoYour own logo: an image you uploaded to QRdx (PNG or JPEG, up to 1 MB), by file id. Needs the workspace's API key on this connection (Authorization: Bearer qrdx_…).
community_itemNoStart from a community theme or frame by id, such as frame:wifi-card (search_community finds them); style options you set win over it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / style / properties / backdrop
      Added value: +{
      +  "description": "Solid color outside the rounded background (see-through by default); drawn only with bgRadius",
      +  "maxLength": 64,
      +  "type": "string"
      +}
    • addedInput schema / properties / style / properties / bgRadius
      Added value: +{
      +  "description": "Corner radius of the background as a share of the code's width, 0 to 0.5 (0.5 is a disc); capped so the quiet zone (margin) keeps the code's corners, so it needs a margin",
      +  "maximum": 0.5,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / style / properties / eyeGradient
      Added value: +{
      +  "description": "Where the eyes' gradients run: corner (each eye on its own, the default) or code (across the whole code, so eyes continue the dots' gradient)",
      +  "enum": [
      +    "corner",
      +    "code"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / style / properties / eyeShapes
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Per-eye shapes: { topLeft, topRight, bottomLeft }, each { outer, inner } (an eye frame and an eye center shape)",
      +  "properties": {
      +    "bottomLeft": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "inner": {
      +          "description": "The eye's center shape",
      +          "enum": [
      +            "square",
      +            "rounded",
      +            "circle",
      +            "message",
      +            "message-reverse",
      +            "diya",
      +            "diya-reverse",
      +            "rounded-triangle",
      +            "leaf",
      +            "drop",
      +            "plus",
      +            "cross-rounded",
      +            "hexagon",
      +            "octagon",
      +            "flower",
      +            "heart",
      +            "squircle",
      +            "dots",
      +            "extra-rounded",
      +            "leaf-reverse",
      +            "drop-reverse",
      +            "diamond",
      +            "star",
      +            "banner"
      +          ],
      +          "type": "string"
      +        },
      +        "outer": {
      +          "description": "The eye's frame shape",
      +          "enum": [
      +            "square",
      +            "rounded",
      +            "gear",
      +            "circle",
      +            "diya",
      +            "extra-rounded",
      +            "message",
      +            "pointy",
      +            "leaf",
      +            "drop",
      +            "octagon",
      +            "bevel",
      +            "squircle",
      +            "cushion",
      +            "shield",
      +            "petal",
      +            "leaf-reverse",
      +            "curly"
      +          ],
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "topLeft": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "inner": {
      +          "description": "The eye's center shape",
      +          "enum": [
      +            "square",
      +            "rounded",
      +            "circle",
      +            "message",
      +            "message-reverse",
      +            "diya",
      +            "diya-reverse",
      +            "rounded-triangle",
      +            "leaf",
      +            "drop",
      +            "plus",
      +            "cross-rounded",
      +            "hexagon",
      +            "octagon",
      +            "flower",
      +            "heart",
      +            "squircle",
      +            "dots",
      +            "extra-rounded",
      +            "leaf-reverse",
      +            "drop-reverse",
      +            "diamond",
      +            "star",
      +            "banner"
      +          ],
      +          "type": "string"
      +        },
      +        "outer": {
      +          "description": "The eye's frame shape",
      +          "enum": [
      +            "square",
      +            "rounded",
      +            "gear",
      +            "circle",
      +            "diya",
      +            "extra-rounded",
      +            "message",
      +            "pointy",
      +            "leaf",
      +            "drop",
      +            "octagon",
      +            "bevel",
      +            "squircle",
      +            "cushion",
      +            "shield",
      +            "petal",
      +            "leaf-reverse",
      +            "curly"
      +          ],
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "topRight": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "inner": {
      +          "description": "The eye's center shape",
      +          "enum": [
      +            "square",
      +            "rounded",
      +            "circle",
      +            "message",
      +            "message-reverse",
      +            "diya",
      +            "diya-reverse",
      +            "rounded-triangle",
      +            "leaf",
      +            "drop",
      +            "plus",
      +            "cross-rounded",
      +            "hexagon",
      +            "octagon",
      +            "flower",
      +            "heart",
      +            "squircle",
      +            "dots",
      +            "extra-rounded",
      +            "leaf-reverse",
      +            "drop-reverse",
      +            "diamond",
      +            "star",
      +            "banner"
      +          ],
      +          "type": "string"
      +        },
      +        "outer": {
      +          "description": "The eye's frame shape",
      +          "enum": [
      +            "square",
      +            "rounded",
      +            "gear",
      +            "circle",
      +            "diya",
      +            "extra-rounded",
      +            "message",
      +            "pointy",
      +            "leaf",
      +            "drop",
      +            "octagon",
      +            "bevel",
      +            "squircle",
      +            "cushion",
      +            "shield",
      +            "petal",
      +            "leaf-reverse",
      +            "curly"
      +          ],
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / style / properties / halo
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "A light rim around the dark modules and eyes. Drawn only on an opaque bgColor (no picture), in a color at least as light as #d1d5db and no lighter than any background color; otherwise the code is drawn without it (the scan score's halo check says why)",
      +  "properties": {
      +    "color": {
      +      "description": "The rim's color (default #e5e7eb): at least as light as #d1d5db and no lighter than the background; drawn opaque (alpha is dropped)",
      +      "maxLength": 64,
      +      "type": "string"
      +    },
      +    "width": {
      +      "description": "Width in modules, 0.1 to 0.5 (default 0.25)",
      +      "maximum": 0.5,
      +      "minimum": 0.1,
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / style / properties / shadow
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "A see-through copy of the dark modules and eyes drawn under them, shifted a fraction of a module",
      +  "properties": {
      +    "color": {
      +      "description": "The shadow's color (default black)",
      +      "maxLength": 64,
      +      "type": "string"
      +    },
      +    "dx": {
      +      "description": "Shift across, in modules, -0.3 to 0.3 (default 0.2)",
      +      "maximum": 0.3,
      +      "minimum": -0.3,
      +      "type": "number"
      +    },
      +    "dy": {
      +      "description": "Shift down, in modules, -0.3 to 0.3 (default 0.2)",
      +      "maximum": 0.3,
      +      "minimum": -0.3,
      +      "type": "number"
      +    },
      +    "opacity": {
      +      "description": "0.1 to 0.4 (default 0.3)",
      +      "maximum": 0.4,
      +      "minimum": 0.1,
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well past the annotations: it discloses the validation behavior, the scan-score check, and the repair loop with its exact bound ("at most 3 repairs, then a classic black-on-white code"). It also enumerates the return payload (score, changes and why, qrdxStyle, playground_url, PNG, SVG), which is not visible anywhere else since there is no output schema, and it notes the API-key requirement for uploaded logos.

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

Conciseness3/5

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

Purpose is front-loaded in the first clause, and the repair/return facts earn their space. However the long middle enumeration ("colors and gradients, dot, eye and eye center shapes, a built-in call-to-action frame...") is a multi-clause run-on that largely repeats the schema, making the paragraph denser than it needs to be.

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?

For a tool this complex — 7 params, deeply nested style and content objects, no output schema — the description covers the missing pieces: what is validated, what is repaired, what is returned, and the fallback when the design cannot be made scannable. An agent has enough to invoke it correctly without reading further docs.

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% and the nested style/content objects are documented in depth, so the schema already carries the parameter burden. The description adds the routing hint toward list_options for accepted values and restates precedence ("style options you set win over it"), but the bulk of the design vocabulary it enumerates duplicates what the schema already says.

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 ("Design a QR code") and then scopes it precisely: any content type, full style control, presets or community items, validation plus scan-score repair. It also positions the output relative to siblings, noting the style JSON is "ready for save_template and generate_qr_code", so an agent can tell this is the design/preview step rather than the render step.

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?

Gives a concrete prerequisite ("Call list_options first for the accepted values") and names two valid starting points (built-in preset, community item found via search_community). It implies rather than states the handoff rule — that you call generate_qr_code or save_template afterwards — so there is clear context but no explicit when-not-to-use.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.