Skip to main content
Glama

Render a print-ready poster around one QR

qr_poster
Read-onlyIdempotent

Wrap one QR design in a print-ready poster: a4/a5/a6/letter trim, four layouts (minimal, band, card, tent), headline, instruction line, footer, optional logo, 3 mm bleed and crop marks. Returns a vector PDF by default (ready for a print shop) or a png preview at 36-300 dpi. Useful for a table card, a shop window or a hotel desk. The design fields are the same qr_generate takes; fileFormat is the poster's own format, not the code's.

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": "qr_poster"
  }
}

Input Schema

NameRequiredDescriptionDefault
dpiNoResolution of a png poster, 36-300 dpi. Ignored for pdf.
textNoOptional caption rendered below the QR (e.g. a slogan).
bleedNoAdd a 3 mm bleed around the trim. Recommended for professional printing.
footerNoSmall footer under the poster (website, short URL). Blank: none.
contentYesThe text or URL the QR will encode. Required.
logoUrlNoPublic HTTPS URL of a logo image to embed at the center.
eccLevelNoError-correction level (L=7%, M=15%, Q=25%, H=30%). Higher levels survive more damage but are denser.
headlineNoLarge title above the QR. Blank: none.
showLogoNoDraw the design's logo at the top of the poster. Defaults to true.
cropMarksNoDraw crop marks outside the trim.
frameTextNoLabel inside the frame, max 40 characters, any language (e.g. "Scan me", "View the menu"). Defaults to "Scan me".
fileFormatNoPoster output. Defaults to "pdf" (vector, print-ready); "png" is a raster preview.
frameColorNoFrame colour in hex, also the label background. Defaults to "#000000".
frameStyleNoCall-to-action frame around the whole QR with a short label. Never covers the QR or its quiet zone.
accentColorNoBrand colour for the headline, band and card border (hex). Defaults to the frame or module colour.
instructionNoShort line under the QR (e.g. "Point your camera at the code"). Blank: none.
moduleShapeNoShape of the small modules in the QR matrix.
outputWidthNoOutput width in pixels (raster) or viewport units (svg). 64-4096.
outputHeightNoOutput height in pixels (raster) or viewport units (svg). 64-4096.
posterFormatNoTrim size, portrait. Defaults to a4.
posterLayoutNoPoster layout around the code. Defaults to minimal.
primaryColorNoForeground/module color in hex (e.g. "#000000" or "#0a84ff").
frameTextColorNoFrame label colour in hex. Defaults to "#FFFFFF".
backgroundColorNoBackground color in hex (e.g. "#ffffff"). Use "transparent" for no background.
additionalConfigNoEscape hatch: any other QrConfig field the engine accepts (gradient stops, dot rotation, etc.). Merged on top of the structured fields above.
finderInnerShapeNoShape of the inner dot of the three corner finder patterns.
finderOuterShapeNoShape of the outer ring of the three corner finder patterns.

Output Schema

NameRequiredDescriptionDefault
dpiNoRaster resolution, when the output is a png.
formatYesPoster file: "pdf" or "png".
contentNoWhat the QR encodes.
mimeTypeNoMIME type of the poster.
sizeBytesNoPoster size in bytes.
resourceUriNoURI of the embedded PDF resource. PDFs cannot be inlined, so the file travels as a resource block.
posterFormatNoTrim size used (a4, a5, a6, letter).
posterLayoutNoLayout used (minimal, band, card, tent).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, and the description earns credit on top by disclosing the default return type (vector PDF), the png alternative with its 36-300 dpi range, and the 3 mm bleed/crop-mark printing behavior. That is real operational context an agent would otherwise have to infer from the schema alone.

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?

Three sentences, front-loaded with the primary action and closed with the highest-value caveat, with no filler. The middle sentence is a dense feature list, which is efficient but slightly catalogue-like rather than structured.

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 27-parameter tool this covers the essentials: what it renders, the output formats and their defaults, print-specific options, and the relationship to the sibling generator. An output schema exists so return values need no explanation, and remaining detail (e.g. the additionalConfig escape hatch) is adequately documented in the schema itself.

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 the baseline would be 3, but the description adds a genuinely load-bearing clarification: "fileFormat is the poster's own format, not the code's" — a distinction an agent could easily get wrong given the shared design fields with qr_generate. Layout and trim names are reinforced in prose rather than left purely to the enum lists.

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?

Opens with a specific verb and resource ("Wrap one QR design in a print-ready poster") and immediately enumerates the scope: trim sizes, four named layouts, bleed/crop marks, and the two output formats. The final sentence explicitly separates it from qr_generate, so an agent can tell the two apart without opening either schema.

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 concrete usage contexts ("table card, a shop window or a hotel desk") and clarifies the division of labour with qr_generate via the fileFormat caveat. It stops short of an explicit when-not or a named alternative for plain code-only output, so selection is strongly implied rather than fully spelled out.

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.