drucker-mcp-server

Overview Schema Source Related Servers Discussions Admin

Etikett Drucken

etikett_drucken

Prints a configured label to a CUPS/IPP label printer after preview, supporting text lines, QR codes, size, frame, orientation, and up to 20 copies.

Instructions

Druckt ein Etikett auf dem Etikettendrucker – nur auf ausdrücklichen Auftrag, vorher etikett_vorschau.

Gleiche Parameter wie etikett_vorschau, dazu kopien (1–20). Die Rolle wird vor dem Druck gelesen.

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_drucken"
  }
}

Input Schema

Name	Required	Default
`qr`	No
`quer`	No
`kopien`	No
`rahmen`	No
`zeilen`	Yes
`groesse`	No	mittel
`laenge_mm`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Nov 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false, openWorldHint=false and destructiveHint=false, so the description must explain the side effect, and it does: this is a physical print triggered only on explicit instruction after a preview. It also adds that the user role is checked before printing ('Die Rolle wird vor dem Druck gelesen'), a genuine permission behaviour not visible in the annotations. It does not cover failure modes (printer offline, paper out) or whether a queued job can be undone.

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?

Two short sentences with the hard constraint and the prerequisite front-loaded, then the parameter delta. No filler; every clause carries routing, permission, or parameter information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 not be described, and the permission and prerequisite behaviour is covered. The gap is parameter documentation for a seven-parameter write tool, plus no note on printer availability or what happens to a job that fails mid-print.

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

Parameters2/5

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

Schema description coverage is 0% across seven parameters, so the description carries the full burden. It only adds the kopien range (1–20) and otherwise delegates everything to a sibling ('Gleiche Parameter wie etikett_vorschau'), leaving qr, quer, rahmen, zeilen, groesse and laenge_mm unexplained in both the schema and the description.

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?

States a specific verb and resource ('Druckt ein Etikett auf dem Etikettendrucker') and distinguishes the action from the preview sibling by naming etikett_vorschau as the preceding step. It does not explicitly contrast with datei_drucken or druckauftraege, so the sibling separation is implied rather than exhaustive.

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

Usage Guidelines5/5

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

Gives an explicit gating condition ('nur auf ausdrücklichen Auftrag') and an explicit prerequisite ('vorher etikett_vorschau'), which tells the agent both when to call this tool and which sibling must run first. This is exactly the when-to-use versus alternative routing an agent needs.

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

Deploy Server