Skip to main content
Glama

QRavate QR codes

Rattacher un produit GS1

set_gs1_product
DestructiveIdempotent

Rattache le GTIN d’un produit (code EAN) à un QR code dynamique, avec des liens par usage (fiche produit, rappel, notice, allergènes, passeport numérique…) et par langue : le QR suit alors la norme GS1 Digital Link, lisible en caisse dès 2027. L’adresse encodée change : il faut retélécharger le code avant d’imprimer. remove=true retire le produit. Plans Pro et Max. Nécessite l’accès en écriture.

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": {
      "qr": "<qr>"
    },
    "name": "set_gs1_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
qrYes
gtinNoGTIN de 8, 12, 13 ou 14 chiffres, attribué par GS1 (le nombre sous le code-barres).
linksNo
removeNo
forwardNoTransmettre lot, série et date limite à la page ouverte.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnly=false, but the description adds a genuinely non-obvious consequence: the encoded address changes, so the code must be re-downloaded before printing. It also discloses the plan gating and the write-permission requirement. What is missing is any statement of what happens to previously attached links on a repeat call, despite the idempotent hint.

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 dense paragraph that is front-loaded with the purpose, then the reprint warning, the removal mode, and the plan/permission requirements in descending order of importance. No filler sentences; every clause carries operational 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?

For a five-parameter mutation with no output schema, the definition covers the essential behaviour: the standard being applied, the side effect on the encoded URL, the removal mode, and the entitlement prerequisites. Remaining gaps are secondary — the meaning of the required 'qr' argument and the shape of the response on success.

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 only 40%, so the description must compensate: it does explain that 'links' are organised by usage type and language, and that 'remove=true' detaches the product. It says nothing about the required 'qr' parameter, the 'lang'/'title' fields, or the forward flag beyond what the schema already states. Partial compensation only.

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 precise verb and resource: it attaches a product's GTIN/EAN to a dynamic QR code, generating usage-specific links (product sheet, recall, instructions, allergens, DPP) per language under the GS1 Digital Link standard. That is far more specific than a restatement of the title. It does not, however, contrast itself with siblings such as update_destination or set_redirect_rules, so the boundary is left implicit.

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?

Useful context is given — Pro/Max plans and write-access prerequisite — plus the in-tool mode switch 'remove=true retire le produit'. But there is no guidance on when to prefer this over sibling tools that also alter where a QR points, nor any exclusion or failure condition. Usage is implied rather than directed.

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