MCP Label Printer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| print_labelB | Print a label with QR code and text to Brother QL-810W printer. The QR code links to the provided URL, and text shows issue details. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'print_label' follows a clear verb_noun pattern.
One tool is too few for a server named 'MCP Label Printer', which suggests a broader scope for label printing operations. A single tool limits functionality and feels thin for the apparent domain.
The server lacks obvious operations for a label printing domain, such as listing printers, configuring settings, or managing label templates. The single tool provides basic printing but leaves significant gaps in coverage.