Skip to main content
Glama
Sign In
labelixa-mcp

labelixa-mcp

Official
by Labelixa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

convert_zpl_dpi

Rescale ZPL label coordinates between printer resolutions (203/300/600 dpi) and flag embedded bitmap data that is not rescaled.

Instructions

Rescale ZPL coordinates between printer resolutions (203/300/600 dpi). Embedded ^GF/~DG bitmap data is NOT rescaled — when present, a Warnings block precedes the output instead of silently passing.

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": {
      "zpl": "<zpl>"
    },
    "name": "convert_zpl_dpi"
  }
}

Input Schema

NameRequiredDescriptionDefault
zplYesRaw ZPL code to convert
sourceNoSource resolution in dpi (152, 203, 300 or 600)
targetNoTarget resolution in dpi (152, 203, 300 or 600)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / source / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / source / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / target / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / target / minimum
      Added value: +-9007199254740991
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations the description carries the full burden, and it does disclose the most important trait: embedded ^GF/~DG bitmaps are NOT rescaled and a Warnings block is emitted rather than silently passing. That is genuine, non-obvious behavioral context. It stops short of covering error behavior on invalid ZPL or the output shape.

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 sentences, no waste, with the core operation front-loaded and the caveat immediately after. Every clause carries information.

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 3-param transform tool with no output schema, the description tells the agent what is transformed, what is left alone, and that a Warnings block may precede output. Error/failure behavior and the return type are the only notable gaps.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so zpl/source/target and their defaults are already documented. The description adds the resolution set (203/300/600) but actually omits 152, which the schema lists, so it adds little and is slightly narrower than the schema.

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 (rescale ZPL coordinates) plus the dimension being scaled (printer resolution), which no sibling tool covers. It never names an alternative, but the purpose is unmistakable and non-overlapping with zpl_validate/zpl_preview.

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 by the purpose — you call it when moving a label between 203/300/600 dpi printers. There is no explicit when-to-use/when-not guidance, no instruction to validate with zpl_validate first, and no note about what happens if source equals target or the source is mis-declared.

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