Skip to main content
Glama
supvan-e11

supvan-e11

by marco308

preview_label

Render a label image from text, QR code, border, font, alignment, and size settings without printing, returning the picture and preview ID for confirmation.

Instructions

Draw a text label and return a picture of it, and a preview_id, without printing.

text: label text; use \n for a new line (two lines fit comfortably, three is tiny). length_mm: label length along the tape; default is the loaded die-cut label length. font: sans-bold (default), sans, condensed-bold, condensed, serif or mono. size: font height in dots (8 dots per mm, the tape is 96 dots high); default fits the text. align: left, center or right. qr: if set, a QR code holding this text/URL goes at the left end. border: draw a rounded border. invert: white text on black.

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": {
      "text": "<text>"
    },
    "name": "preview_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
qrNo
fontNosans-bold
sizeNo
textYes
alignNocenter
borderNo
invertNo
length_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the two things that matter most: the call has no physical side effect ("without printing") and it returns both an image and a preview_id. The notable gap is that it never explains what the preview_id is for or how long it remains valid, which matters since it is a returned artifact likely consumed by a later print call.

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?

A single front-loaded sentence states purpose and return values, followed by a tight one-line-per-parameter block in schema order. No sentence is decorative and each parameter line contributes either a default, a unit, or a constraint.

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 an eight-parameter, no-annotation, no-output-schema tool, the description is largely sufficient: every parameter is explained and the return artifacts are named. The remaining gap is the lifecycle and intended use of preview_id, which an agent would need before chaining this into a print step.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description fully compensates by documenting all eight parameters with defaults, units, and constraints: dots-per-mm and 96-dot tape height for size, the loaded die-cut length as the length_mm default, allowed font and align values, and the practical limit of two comfortable lines. This adds real meaning well beyond bare JSON types.

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?

"Draw a text label and return a picture of it, and a preview_id, without printing" gives a specific verb (draw), resource (text label), and explicitly bounds the effect as non-printing, which separates it from the print path. It stops short of naming the sibling it is the alternative to, so the distinction must be inferred from the phrase "without printing".

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "without printing" implies this is the safe, iterative path before committing to print_label, but the description never says "use this to preview before printing" or names any alternative. Usage is implied rather than stated, so an agent must infer the workflow ordering itself.

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