Skip to main content
Glama

Cycle Intelligence

by com.cycle-platform

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.

Input Schema

TableJSON 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).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that the tool is deterministic, requires no account, and returns the validity status, normalized GTIN-14, and exact error on failure. This gives the agent a strong model of what to expect without needing to invoke the tool.

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 description is efficient: three sentences, with the main purpose front-loaded and supporting behavior placed at the end. Some parenthetical detail about Sunrise 2027 and DPP is informative but not strictly necessary, keeping it from a perfect score.

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?

The description covers the tool's inputs, outputs, and usage timing, which is strong given there is no output schema. It does not explicitly state what happens when both gtin and digital_link are provided or when neither is provided, which is a minor gap for a tool with zero required parameters.

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%, so the description adds no essential parameter meaning beyond what the schema already documents. It does clarify that only one identifier type (GTIN or Digital Link) is expected at a time, but the individual parameter descriptions already carry the semantic load.

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?

The description names a specific verb ('verify') and a clear resource scope (GTIN/EAN barcode numbers and GS1 Digital Link URLs). It also states the return value and error behavior, which makes the tool's purpose unambiguous and distinguishes it from sibling creation/DPP-readiness tools.

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?

The description gives explicit guidance: use it before printing labels or QR codes to ensure GS1 conformance. It does not name alternative tools or state exclusions, but the context is clear enough for an agent to know when this validation step is appropriate.

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

All Cycle Intelligence toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a distinct purpose: regulatory info, readiness validation, twin creation, DPP issuance, data carrier generation, and identifier validation. No two tools overlap in function; create_product_twin and create_dpp are complementary steps in the same workflow.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: check_, create_, validate_. The verbs are consistent and the nouns clearly indicate the target object or action, making the API predictable and easy to navigate.

Tool Count5/5

With 6 tools, the server is well-scoped for the DPP lifecycle: requirements, readiness, twin creation, DPP issuance, carrier generation, and identifier validation. Each tool is essential and the count is appropriate for the domain.

Completeness4/5

The core workflow of creating a compliant DPP is covered (validate readiness, create twin, create DPP, generate carrier). Missing update/delete operations are likely out of scope for this server, but the absence of a retrieval or listing tool is a minor gap that agents could work around via the returned URLs.

Resources