Skip to main content
Glama

build_gs1_digital_link

Read-onlyIdempotent

Use this tool to turn a GTIN/EAN (plus optional lot and serial number) into a conformant GS1 Digital Link URL, the QR payload required for Sunrise 2027 retail QR codes and EU Digital Product Passport data carriers. If the GTIN check digit is wrong it explains why and suggests the corrected number. Deterministic, no account needed.

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

Input Schema

NameRequiredDescriptionDefault
lotNoOptional batch/lot (GS1 AI 10, ≤20 chars).
baseNoOptional https resolver origin you control; default https://id.cycle-platform.com
gtinYesGTIN-8/12/13/14 or EAN.
serialNoOptional serial number (GS1 AI 21, ≤20 chars).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, and closed-world behavior. The description adds meaningful traits beyond those: deterministic output, no account required, and check-digit validation that explains the failure and suggests a corrected number. It does not describe rate limits or output shape, but the output schema covers the latter.

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?

The description is two tight sentences with the core action front-loaded. The second sentence adds only high-value behavior: validation feedback and no-account determinism. There is no redundant restatement of the title or schema.

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?

With rich annotations and a full output schema, the description needs only to explain purpose and notable behavior, which it does. It covers check-digit handling, determinism, and no authentication. The one gap is that it does not mention the optional base resolver parameter, though the schema documents it fully.

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 description coverage is 100%, so all four parameters are already documented in the input schema. The description reinforces that lot and serial are optional but does not explain the base resolver override or add format details beyond the schema. Baseline 3 is appropriate when the schema carries parameter semantics.

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 states a specific verb and resource: turn a GTIN/EAN plus optional lot and serial into a conformant GS1 Digital Link URL. It contextualizes the output as a QR payload for Sunrise 2027 and EU DPP data carriers, which separates it from validation or resolution siblings. It stops short of explicitly naming the sibling it is not, so a 4 rather than 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?

It gives clear usage context, namely generating the QR payload needed for retail QR codes and Digital Product Passport carriers. However, it does not state when to use this instead of resolve_digital_link, validate_gs1_identifier, or create_data_carrier, nor does it give prerequisites or exclusions. Usage is implied by the scenario rather than routed explicitly.

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