Skip to main content
Glama
Sign In
labelixa-mcp

labelixa-mcp

Official
by Labelixa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cpcl_validate

Validate CPCL label code and return structured JSON diagnostics with findings, positions, and severity so you can identify and fix label syntax issues.

Instructions

Lint/validate CPCL label code and return the structured diagnostics report (findings with positions and severity) as JSON.

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": {
      "cpcl": "<cpcl>"
    },
    "name": "cpcl_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpclYesRaw CPCL code

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.9/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose the important behavioral trait: the return is a structured diagnostics report with positions and severity, in JSON. 'Lint/validate' implies a non-mutating check with no side effects on the input, though the description does not say so explicitly or cover limits on input size.

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?

A single sentence with the action front-loaded, followed immediately by what is returned. No filler, no restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required string parameter), and since no output schema exists, the description usefully compensates by describing the return shape (findings with positions and severity, JSON). An agent has everything needed to call it and interpret the result.

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?

There is a single parameter at 100% schema description coverage ("Raw CPCL code"), so the schema already covers it and baseline 3 applies. The description's phrase "CPCL label code" adds no format, encoding, or size guidance beyond 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?

The description states a specific verb pair ("Lint/validate") and resource ("CPCL label code"), which cleanly separates it from the zpl_validate, epl_validate, and tspl_validate siblings by language. It stops short of explicitly routing callers who don't yet know the label language (e.g., toward language_detect), so it falls just short of a 5.

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 only implied: the tool is for checking CPCL code. There is no statement of when to prefer it over siblings, no mention of what to do with the diagnostics (e.g., fix-and-revalidate), and no exclusion or prerequisite guidance.

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