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

drucker-mcp-server

by Schimmilab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Etikett Rolle

etikett_rolle
Read-only

Reads the label roll currently loaded in the printer, returning its width and whether it is continuous or pre-cut.

Instructions

Liest vom Etikettendrucker, welche Rolle gerade eingelegt ist (Breite, endlos oder vorgestanzt).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "etikett_rolle"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context about what the read returns (media width and whether the roll is endless or pre-cut), but says nothing about failure behavior, e.g. what happens with no roll loaded or an offline printer.

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 with no padding: the verb, the source (label printer), the subject (current roll), and the returned attributes. Nothing is redundant or buried.

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 zero-parameter read with an output schema and read-only annotations, the description covers what the tool reports and where it reads from. The only real omission is error/edge behavior, which is minor given the schema carries the return shape.

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?

There are zero parameters, so semantics get the baseline 4; the description does not need to explain any input. It sensibly spends its words on what the call reports instead.

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 has a specific verb ("Liest") and a specific resource ("welche Rolle gerade eingelegt ist") plus the concrete attributes returned (Breite, endlos oder vorgestanzt). That distinguishes it from drucker_liste, etikett_vorschau and etikett_drucken, though it never names a sibling explicitly.

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

Usage Guidelines2/5

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

It never says when to call this instead of drucker_liste (printer inventory) or etikett_vorschau (label preview), and it states no prerequisites or exclusions. An agent can infer it returns the currently loaded media, but nothing in the text explicitly routes it against the siblings.

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