Skip to main content
Glama
Sign In
drucker-mcp-server

drucker-mcp-server

by Schimmilab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Etikett Vorschau

etikett_vorschau
Read-only

Renders a label as a PNG matching the loaded roll without printing, so you can check the layout before sending it to the printer.

Instructions

Rendert ein Etikett passend zur eingelegten Rolle als PNG, OHNE zu drucken.

zeilen: 1–6 Textzeilen. {datum} = heute. groesse: Schrift-Obergrenze 'klein' (~4 mm), 'mittel' (~7 mm, Standard) oder 'gross' (füllt die Rollenbreite). Auf Endlosrollen bestimmt sie damit auch die Länge des Etiketts. laenge_mm: feste Länge, nur bei Endlosrolle; die Schrift wird dann so groß wie hineinpasst. quer: Text quer zur Rolle, für kurze Etiketten, die quer aufgeklebt werden. laenge_mm ist dann die Etikett-Höhe (z. B. 25 → 25 × 38 mm auf der 38-mm-Rolle), kein Abschneiden nötig. qr: optionaler Inhalt für einen QR-Code links (z. B. eine URL).

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": {
      "zeilen": "<zeilen>"
    },
    "name": "etikett_vorschau"
  }
}

Input Schema

NameRequiredDescriptionDefault
qrNo
querNo
rahmenNo
zeilenYes
groesseNomittel
laenge_mmNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only and closed-world behavior, and the description goes well beyond them: it explains that on continuous rolls the font size determines label length, that fixed length shrinks the font to fit, and that nothing is truncated in landscape mode. It omits the effect of the 'rahmen' parameter, which is a visible rendering behavior left undisclosed.

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?

The core promise is front-loaded in the first line and the rest is a compact, label-per-parameter breakdown with no filler. Lines are dense with parenthetical detail, which is efficient but slightly hard to scan as prose.

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?

With an output schema present, the description needn't explain the returned PNG, so it correctly concentrates on sizing, roll-type interaction, orientation, and QR content. The only shortfall is the undocumented 'rahmen' flag, which an agent might otherwise set blindly.

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 0%, so the description carries the full burden, and it does document five of six parameters with real meaning: the 1–6 line range with a {datum} placeholder, approximate millimeter sizes per groesse value, conditional applicability of laenge_mm, the height-interpretation of laenge_mm under quer, and QR placement on the left side. The 'rahmen' parameter is never mentioned, leaving a documented gap below the baseline for full coverage.

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 (renders a label as PNG) and immediately scopes it with 'OHNE zu drucken', which cleanly separates it from the printing sibling etikett_drucken. An agent can pick this tool without inspecting any 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?

The preview-vs-print distinction is explicit via 'OHNE zu drucken', and the 'passend zur eingelegten Rolle' clause tells the agent it must be used with a loaded roll. It never names etikett_drucken as the follow-up alternative, so routing is implied rather than spelled out.

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

Deploy Server

Other Tools