Skip to main content
Glama
supvan-e11

supvan-e11

by marco308

print_label

Prints a label from an existing preview after the user approves it, with adjustable copies and print density.

Instructions

Print a label the user has seen: exactly the picture from preview_label or preview_freezer_label. Show the user the preview and print only once they're happy.

preview_id: from the preview, made in the last 10 minutes. Each preview prints once; preview again to print it again. copies: how many to print (1-20). density: darkness, 1-15 (default 4); raise it if the print is faint.

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": {
      "preview_id": "<preview_id>"
    },
    "name": "print_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
copiesNo
densityNo
preview_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 well: it discloses the 10-minute preview TTL, the single-use property of a preview_id, copies and density ranges, the density default, and a tuning heuristic (raise density if faint). It omits any statement about permissions, printer state requirements, or error behavior, which keeps it from a 5.

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?

Purpose and the preview-first safety instruction are front-loaded, and every clause earns its place. The parameter notes are stacked as bare lines rather than structured bullets, which makes the dense TTL/one-shot rule slightly harder to scan, but there is no filler text.

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?

An output schema exists, so return values need no explanation, and the description covers the non-obvious operational semantics (preview lifetime, single use, ranges) that an agent could otherwise get wrong. The remaining gap is failure and printer-state handling, which matters for a physical-actuation tool with no annotations.

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%, so the description must supply all parameter meaning, and it does: preview_id gains provenance, a 10-minute validity window and single-use semantics; copies gains a 1-20 bound; density gains a 1-15 range, a default of 4, and actionable tuning advice. This is meaning the schema does not convey anywhere.

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 ("Print a label") and pins down scope precisely: "exactly the picture from preview_label or preview_freezer_label." It names the sibling tools whose output it consumes, so an agent can tell it apart from preview_label and feed_tape without opening a 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 an explicit precondition and workflow: show the preview, print only once the user is happy, and re-preview to print again. The one-shot-per-preview rule is a clear usage constraint. It does not address what to do when a print fails (e.g., checking printer_status or feed_tape), so guidance stops just short of covering failure paths.

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