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

drucker-mcp-server

by Schimmilab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Druckauftrag Abbrechen

druckauftrag_abbrechen
Destructive

Cancel an open print job by passing its job ID from the print queue. Use it to stop pending or active label or document prints when a job is no longer needed.

Instructions

Bricht einen offenen Druckauftrag ab (ID aus druckauftraege, z. B. 'Brother_QL_820NWB-109').

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": {
      "auftrag": "<auftrag>"
    },
    "name": "druckauftrag_abbrechen"
  }
}

Input Schema

NameRequiredDescriptionDefault
auftragYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is covered structurally. The description contributes one real behavioral constraint beyond that — only open jobs can be cancelled — but says nothing about irreversibility, permission requirements, or what happens when the job is already completed or the ID is unknown.

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 pairs the action with its precondition, and the parenthetical carries exactly the two pieces of information the empty schema lacks: where to get the ID and what it looks like. Nothing is padded.

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, return values need no explanation, and annotations cover the destructive profile. What remains thin is failure behavior (unknown or non-open ID) and whether cancellation can be undone, which an agent may need for retry decisions.

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

Parameters4/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 carry the parameter meaning, and it does: it names the provenance of the value (ID from druckauftraege) and gives a concrete example format ('Brother_QL_820NWB-109'). That materially reduces the chance of passing a display name or label identifier instead of a job ID.

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 ('bricht einen offenen Druckauftrag ab') and narrows the scope to open jobs, which separates it from creation-side siblings like etikett_drucken or datei_drucken. It does not name an alternative tool directly, so it falls just short of full sibling differentiation.

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?

Usage is implied rather than spelled out: the job must be 'offen', and the parenthetical tells the agent to obtain the ID from druckauftraege, which is a practical routing hint. There is no explicit when-not guidance, e.g. what to do for already-printed or unknown jobs.

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