Skip to main content
Glama

gtin-hierarchy

GTIN hierarchy: GTIN-8/12/13/14 forms, GS1 prefix, packaging-level link — Takes up to 100 GTINs and, for an agent reconciling a product feed or order lines, validates each check digit, converts it to the 14-digit form, reads the indicator digit and GS1 Prefix (restricted-circulation, ISBN/ISSN range, coupon), and, when a parent GTIN is given, checks the two share one base item (the packaging-level link). It does not look up the brand owner, the product or the country of

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": {
      "items": "<items>"
    },
    "name": "gtin-hierarchy"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it discloses the 100-GTIN batch cap and the implicit read-only nature of validation, plus which classifications are examined. It does not say what happens to an invalid check digit (per-item error vs. whole-call failure), nor anything about failure modes or 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.

Conciseness3/5

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

Front-loaded with a redundant label ("GTIN hierarchy:") and then one long em-dash-chained sentence. More damaging, the text is cut off mid-clause ("the country of"), so the exclusion sentence never finishes.

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?

There is no output schema, so the description should indicate what comes back per GTIN (validity, 14-digit form, prefix classification, parent-match result); it never does. The input side is adequately covered, but the return-value side is missing for a batch-of-up-to-100 tool.

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

Parameters4/5

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

Schema description coverage is reported as 0%, so the description must compensate; it explains the batch cap of 100, that each entry is a GTIN string, and that the optional parent must be a packaging level of the same base item — meaning the schema alone would not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (GTIN-8/12/13/14) and concrete operations: check-digit validation, conversion to 14-digit form, indicator-digit and GS1 Prefix interpretation, and parent/child packaging-level verification. An agent can tell exactly what the tool computes without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Frames the calling context ("for an agent reconciling a product feed or order lines") and adds an explicit exclusion: it does not look up brand owner, product, or country. No alternative sibling is named, but the when-to-use and when-not picture is otherwise clear.

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