Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_ecom_gtin_upc_validator

Validate GTIN-8/12/13/14 (UPC/EAN) check digits and convert barcode formats to confirm product codes are correctly structured before use.

Instructions

[E-Commerce Intelligence] Validate GTIN-8/12/13/14 (UPC/EAN) check digits and convert formats Measured p50 11 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://ecom.caelaralabs.com.

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": "caelara_ecom_gtin_upc_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesBarcode digits

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses performance characteristics (p50 11 ms, p95 15 ms) and the backing endpoint, but it omits what matters more for a validator: whether an invalid check digit yields an error or a result field, and what 'convert formats' actually returns or requires.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in a single compact sentence with no filler. The appended latency statistics and endpoint URL are terse but compete with the functional information, which is why this falls short of a 5.

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

Completeness3/5

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

For a simple one-parameter tool this is close, but there is no output schema, so the description should explain what comes back (validity verdict, normalized/converted code). The unresolved mechanics of format conversion leave a real gap for an agent deciding how to call it.

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% and the single parameter is documented as 'Barcode digits', so the baseline is 3. The description adds some framing by enumerating accepted standards (GTIN-8/12/13/14), but the advertised format conversion has no corresponding parameter, leaving unclear how a target format is selected.

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 ('Validate') plus a precise resource ('GTIN-8/12/13/14 (UPC/EAN) check digits') and adds a second capability ('convert formats'), which is far more specific than a generic validator. It does not explicitly differentiate itself from nearby tools such as caelara_ecom_sku_normalizer, though the barcode-standard framing makes the distinct scope reasonably 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?

There is no when-to-use guidance, no prerequisites, and no named alternative. An agent cannot tell from the description whether to reach for this versus the SKU normalizer when handling product identifiers, nor under what conditions format conversion should be requested.

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