Skip to main content
Glama
Sign In
labelixa-mcp

labelixa-mcp

Official
by Labelixa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

language_detect

Classify raw label code as ZPL, EPL, TSPL, or CPCL and return the detected language with a confidence tier and signal codes for validation or conversion.

Instructions

Detect which printer language raw label code is written in (ZPL, EPL, TSPL or CPCL). Heuristic: returns the language plus a confidence TIER (high/medium/low) and signal codes — not a probability.

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": {
      "code": "<code>"
    },
    "name": "language_detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesRaw label code to classify

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.0

TDQS

A3.6/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 does meaningful work: it discloses the method is a 'Heuristic' and explicitly warns that the result is a confidence TIER plus signal codes, 'not a probability' — setting correct expectations about reliability. It stops short of stating determinism, whether empty/garbage input errors, or performance characteristics.

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 dense sentences with zero filler: the purpose and the candidate set come first, the return-shape caveat second. Every clause carries information the agent needs.

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 one-parameter, no-annotation tool with no output schema, the description covers the essential ground by explaining the return shape (language + tier + signal codes) and the heuristic nature. Only the routing guidance to the sibling validators is missing.

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?

One parameter with 100% schema description coverage ('Raw label code to classify'), so the schema already documents it fully. The description adds nothing about input format, size limits, or how mixed-language code is handled, so baseline 3 applies.

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 ('Detect') and resource ('which printer language raw label code is written in') and enumerates the candidate languages (ZPL, EPL, TSPL, CPCL), so the agent knows exactly what comes back. It never names the sibling validators (zpl_validate, epl_validate, etc.) or positions itself relative to them, so sibling differentiation is only inferable.

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?

The description is purely definitional: no statement of when to call this versus the four *_validate tools, no prerequisites, and no guidance on what to do with a 'low' tier result. An agent must infer the triage role from the sibling names alone.

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