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

drucker-mcp-server

by Schimmilab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Datei Drucken

datei_drucken

Print PDF, Markdown, or HTML documents with options for color, duplex, copies, page ranges, and printer selection; Markdown/HTML is converted to A4 PDF via headless Chrome.

Instructions

Druckt PDF, Markdown (.md) oder HTML – nur auf ausdrücklichen Auftrag.

Markdown/HTML wird vorher per Chrome headless zu einem A4-PDF. farbe=False druckt schwarz-weiß. seiten z. B. '1-3,5'. drucker leer = DRUCKER_DOKUMENT bzw. CUPS-Standard. Mehr als 20 Druckseiten (Seiten × Kopien) nur mit bestaetigt=True – vorher den Nutzer fragen.

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": {
      "pfad": "<pfad>"
    },
    "name": "datei_drucken"
  }
}

Input Schema

NameRequiredDescriptionDefault
pfadYes
farbeNo
duplexNo
kopienNo
seitenNo
druckerNo
bestaetigtNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false) it discloses the internal pipeline (Markdown/HTML converted by headless Chrome to A4 PDF), the color and page-range semantics, the printer fallback chain (DRUCKER_DOKUMENT then CUPS default), and an explicit safety gate above 20 pages. It does not say what the response contains or how print jobs are tracked, but the output schema covers returns.

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?

Four short lines, front-loaded with the core action and the 'explicit request only' constraint, then the conversion detail, then the confirmation rule. No sentence is redundant.

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 7-parameter side-effecting print tool with an output schema and annotations already present, the description covers the risky parts well (confirmation threshold, printer resolution, conversion). The missing duplex semantics and any statement about async job handling are the main gaps.

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 parameter burden, and it explains farbe, seiten (with the '1-3,5' example), drucker (fallback behavior) and bestaetigt (the page x copies threshold). duplex is never mentioned, kopien is only implied via the threshold formula, and pfad's accepted paths/formats are not defined, leaving real gaps.

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?

The description states a specific verb and resource: printing PDF, Markdown or HTML files, with the conversion step named. This implicitly separates it from the label-printing siblings (etikett_drucken, etikett_vorschau), but it never names an alternative explicitly, so the differentiation is left to inference.

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?

It sets clear preconditions: print only on explicit request, and ask the user first when pages x copies exceeds 20 (bestaetigt=True). It gives no routing guidance versus the sibling tools such as druckauftraege or etikett_drucken, which keeps it from a 5.

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