Skip to main content
Glama

Caelara Labs E-Commerce Intelligence

gtin_upc_validator

Validate GTIN-8/12/13/14 (UPC/EAN) check digits and convert formats

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

Input Schema

NameRequiredDescriptionDefault
codeYesBarcode digits

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the two behaviors (check-digit validation and format conversion) but says nothing about what happens on an invalid code, what the target format of the conversion is, or whether the response is a boolean, a converted string, or both.

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?

A single front-loaded sentence with no filler or repetition. Slightly penalized because 'convert formats' is compressed to the point of vagueness — it does not say to what or how.

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 one-parameter tool with no annotations and no output schema, the definition covers scope (which GTIN lengths) but not the return shape or failure behavior, which an agent needs since nothing else documents it. Adequate but with a clear gap around outputs.

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% for the single 'code' parameter, so the baseline is 3. The description adds the accepted GTIN lengths and that the digits are barcode digits, but leaves ambiguous how the 'convert formats' capability is selected when no target-format parameter exists.

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 specific verbs and resource: validate check digits for GTIN-8/12/13/14 (UPC/EAN) and convert formats. The accepted symbologies are enumerated, so an agent knows exactly what inputs it handles. It does not explicitly distinguish itself from a potentially related sibling like sku_normalizer, which keeps it from 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: an agent can infer this is the tool for checking barcode validity or converting a barcode's format, but the description gives no explicit when-to-use conditions, no prerequisites, and no exclusions relative to alternatives in the catalog.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources