Skip to main content
Glama

create_data_carrier

Use this tool to generate the printable data carrier (QR content) of a twin: a GS1 Digital Link URL (Sunrise 2027 standard) if you pass a valid GTIN, or a serialized twin URL fallback without one. The URL resolves to the product's live twin the moment it is created - it is connected, not a loose QR. Invalid GTINs are rejected before printing. Requires an authorised organisation-bound Cycle connection (OAuth or API key). OPTIONAL: pass allocation={channel|retailer, shipment?, region?, units?} to link the serial to its intended retail channel (channel-aware serialization: future scans of that unit resolve their channel, always labelled INFERRED).

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": "create_data_carrier"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuNo
gtinNo
serialNo
allocationNo
product_idNo
idempotency_keyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=false, openWorld=false), the description discloses that the emitted URL resolves to the live twin immediately, that invalid GTINs are rejected before printing, that an authorised organisation-bound connection (OAuth or API key) is required, and that channel allocations surface as INFERRED labels on future scans. Those are real behavioral facts an agent cannot get from the annotations.

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?

Front-loaded with the core action and output, then constraints, then the optional allocation block — a sensible order. The prose is dense but every sentence carries information; only the parenthetical '(Sunrise 2027 standard)' and 'connected, not a loose QR' lean slightly toward marketing.

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 tool is moderately complex (6 params, a nested allocation object, a mutation), and the description covers the important semantics: output format, validation behavior, auth requirement, and the optional channel linkage. With an output schema present, return values need not be explained, but the undocumented sku/serial/product_id/idempotency_key inputs remain a gap.

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 0% across six parameters, so the description must carry the load; it explains gtin (validated, drives URL format) and enumerates every allocation sub-field (channel, retailer, shipment, region, units). It says nothing about sku, serial, product_id, or idempotency_key, leaving four top-level parameters with no meaning anywhere.

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 opens with a specific verb and resource: 'generate the printable data carrier (QR content) of a twin', and distinguishes two output modes (GS1 Digital Link URL with a valid GTIN vs. a serialized twin URL fallback). It never names the adjacent siblings build_gs1_digital_link or resolve_digital_link, so an agent must infer the boundary itself.

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?

It gives clear trigger conditions: use it to produce printable QR content, pass a GTIN for the standards-compliant link or omit it for the fallback, and optionally pass allocation for channel-aware serialization. It stops short of stating when NOT to use it or which sibling to reach for instead (e.g. link building vs. resolution).

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