Skip to main content
Glama

validate_gs1_identifier

Read-only

Use this tool to verify a GTIN/EAN barcode number (check digit, GS1 mod-10) or a GS1 Digital Link URL (the QR standard behind Sunrise 2027 retail QR codes and DPP data carriers). Returns whether the identifier is valid, the normalised GTIN-14, and the exact error if not. Use it before printing labels or QR codes so they conform to GS1. Deterministic, no account needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "validate_gs1_identifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
gtinNoGTIN/EAN-8/12/13/14 to validate.
digital_linkNoGS1 Digital Link URL to validate (e.g. https://id.example.com/01/09506000134352/21/SER123).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds value beyond them: it states the tool is deterministic and requires no account, and that it returns the normalised GTIN-14 plus the exact error when invalid. These are behavioral facts an agent would otherwise have to guess at.

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?

Three tightly packed sentences with the capability front-loaded, followed by the return contract and then the recommended usage point. There is no boilerplate or repeated information.

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?

An output schema exists, so the brief mention of return values is sufficient rather than required. The description covers no-auth access, determinism, and both input types; the only real gap is guidance on the mutual exclusivity of the two optional parameters.

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 100% so the baseline is 3, but the description adds meaning by clarifying the two inputs are alternatives ('a GTIN/EAN ... or a GS1 Digital Link URL') and by explaining what a Digital Link is and what formats the GTIN takes. It still does not state what happens if both parameters are supplied simultaneously.

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 (verify) and two concrete resources (GTIN/EAN barcode check digit, GS1 Digital Link URL), plus what it returns. It does not explicitly contrast itself with siblings like build_gs1_digital_link or resolve_digital_link, but the validation-only scope makes the distinction inferable.

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?

Gives one clear usage moment – 'Use it before printing labels or QR codes so they conform to GS1' – which is useful context. It offers no exclusions or explicit pointers to alternative tools for adjacent needs such as building or resolving a link.

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