labelprint
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LABELPRINT_DPI | No | Printer DPI. | |
| LABELPRINT_ADDRESS | No | Printer address (e.g., MAC address for Bluetooth, serial port for serial). | |
| LABELPRINT_DENSITY | No | Print density. | |
| LABELPRINT_WIDTH_MM | No | Media width in millimeters. | |
| LABELPRINT_HEIGHT_MM | No | Media height in millimeters. | |
| LABELPRINT_TRANSPORT | No | Transport type: auto, rfcomm, bluetooth, or serial. | |
| LABELPRINT_MAX_WIDTH_PX | No | Maximum print width in pixels. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| labelprint_doctorA | Check local config, serial ports, and which transport this machine would use. Does not open the printer. Use this first when setup is unclear. |
| labelprint_list_portsA | List serial device nodes visible on this machine. |
| labelprint_statusB | Open the configured local printer and return identity, power, and on-device media chip data. Media size is not fetched from the internet. If a barcode is present, match it against the local config table or pass width_mm/height_mm when printing. |
| labelprint_renderA | Render a preview PNG (title, body, and/or QR). Does not print. |
| labelprint_printA | Print a PNG, or render title/body/QR and print that. Consumes physical labels. confirm must be true. Preview with labelprint_render first. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: doctor performs setup diagnostics without opening the printer, list_ports only enumerates serial nodes, status opens the printer for identity/media, render previews, and print consumes labels. The doctor/list_ports boundary is explicitly clarified by the descriptions.
All tools use the same labelprint_ prefix and snake_case, making them predictable and grouped. Minor inconsistency: doctor and status are noun-like diagnostics while render/print/list_ports are action verbs.
Five tools is well-scoped for a label-printing server: three diagnostic tools, one preview tool, and one print tool. Each earns its place without redundancy.
The surface covers diagnostics, preview, and printing, which are the core lifecycle operations. Minor gaps include no explicit configuration-setting or job-management tool, though doctor covers config inspection.