Skip to main content
Glama
Sign In
p21

p21

by mocchan0221
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Save a label file

p21_save_label
Destructive

Save a label as a .p21.json file for opening in the GUI or printing with the CLI, and return the absolute path.

Instructions

Save a label as a .p21.json file (relative paths are relative to the server's working directory) so the user can open it in the GUI or print it with the CLI. Returns the absolute path.

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": {
      "label": "<label>",
      "path": "<path>"
    },
    "name": "p21_save_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesMust end in .json
labelYesNelko P21 label. Coordinates are printer dots (203 dpi, ~8 dots/mm) on the design canvas. Landscape 14x40 mm canvas = 284 x 96 dots (x across the label length, y across the 12 mm printable tape width). Canvas width = round(length_mm * 7.1) for other lengths. Output is pure black/white.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, so the write/overwrite risk is already flagged structurally. The description usefully adds path-resolution semantics and the return value, but it never says whether an existing file at `path` is overwritten or whether parent directories are created — the one behavioral detail that matters most for a destructive save.

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?

Two short sentences, front-loaded with the action and format, followed by the return value. Nothing redundant and no filler.

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 only two parameters and no output schema, the description covers purpose, path resolution, and return value adequately. The remaining gap is overwrite/directory-creation behavior for a destructive write, which would be worth one more sentence.

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 coverage is 100%, so the label object is fully self-documenting. The description still earns credit beyond the schema by explaining that relative paths resolve against the server's working directory and that the absolute path is returned, which the schema's 'Must end in .json' note does not cover.

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 concrete verb+resource: saving a label as a .p21.json file, plus the downstream uses (open in GUI, print with CLI). It doesn't explicitly contrast itself with the sibling p21_save_template, so an agent must infer the label-vs-template split, but the format-specific wording makes the intent unambiguous.

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?

The stated downstream purposes (GUI open, CLI print) imply when to reach for this tool, but there is no explicit when-not guidance and no alternative sibling is named (e.g. p21_save_template or p21_print). Usage must be inferred rather than read.

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