Skip to main content
Glama

Normalize a GTIN

bpj_gtin_normalize
Read-onlyIdempotent

Validate an 8-, 12-, 13- or 14-digit GS1 trade identifier and normalize it to GTIN-14.

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": {
      "value": "<value>"
    },
    "name": "bpj_gtin_normalize"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavior beyond that by specifying which lengths are accepted and that the result is always GTIN-14. It omits what happens on invalid input (error vs. null) and whether zero-padding or check-digit verification is performed, which are the main behavioral unknowns for a validation tool.

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, front-loaded with the operation and immediately followed by input constraints and output form. Nothing is redundant and nothing needs to be trimmed.

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 pure function with rich annotations and no output schema, the definition supplies the essential input contract and output target. The remaining gap is failure-mode behavior, which matters because the tool's stated job is validation.

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 coverage is 0% and the single parameter is a generically titled "value" string capped at 240 characters, so the description carries the burden. It does compensate substantially by defining the accepted digit lengths and the semantic domain (GS1 trade identifier), though it does not say whether separators such as hyphens or spaces are tolerated.

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 names a specific pair of operations (validate, normalize) on a specific resource (GS1 trade identifier) and states the accepted input lengths and the GTIN-14 output form. It does not reference the closely related sibling bpj_product_gtin_metadata, so an agent must infer the split from the name alone.

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 to call when it holds a raw GTIN of 8/12/13/14 digits. There is no statement of when to prefer it over siblings or what to do with a non-GTIN identifier, and no prerequisites are given.

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.