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 organisation 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. Changed10 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / allocation / additionalProperties
      Added value: +false
    • removedInput schema / properties / allocation / description
      Removed value: -"optional intended retail channel: {channel, retailer, shipment, region, units}"
    • addedInput schema / properties / allocation / properties
      Added value: +{
      +  "channel": {
      +    "maxLength": 80,
      +    "type": "string"
      +  },
      +  "region": {
      +    "maxLength": 80,
      +    "type": "string"
      +  },
      +  "retailer": {
      +    "maxLength": 80,
      +    "type": "string"
      +  },
      +  "shipment": {
      +    "maxLength": 80,
      +    "type": "string"
      +  },
      +  "units": {
      +    "maximum": 100000000,
      +    "minimum": 0,
      +    "type": "integer"
      +  }
      +}
    • addedInput schema / properties / gtin / maxLength
      Added value: +120
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "maxLength": 120,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / product_id / maxLength
      Added value: +120
    • addedInput schema / properties / serial / maxLength
      Added value: +20
    • addedInput schema / properties / sku / maxLength
      Added value: +120
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "anyOf": [
      +    {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    {
      +      "required": [
      +        "created",
      +        "carrier"
      +      ]
      +    }
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / allocation
      Added value: +{
      +  "description": "optional intended retail channel: {channel, retailer, shipment, region, units}",
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (which only say readOnly=false, destructive=false, openWorld=false). It discloses the auth prerequisite (organisation API key), pre-print validation behavior (invalid GTINs rejected), the live-resolution property of the URL, and the important caveat that channel data from allocation is always labelled INFERRED.

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 the GTIN/no-GTIN branching, then auth and the optional allocation block. A few phrases are decorative ("it is connected, not a loose QR") but they still convey a real behavioral property, so little is truly wasted.

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 mutating tool with a nested object, an output schema, and partial annotation coverage, the description covers output modes, auth, validation, and the optional channel-linking semantics. Gaps remain around the undocumented identifier parameters and idempotency behavior, but nothing critical to correct invocation is missing.

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%, so the description must carry parameter meaning: it explains gtin (drives Digital Link generation), serial (the serialized identifier), and it enumerates the allocation sub-fields (channel, retailer, shipment, region, units). However, sku, product_id, and idempotency_key are never mentioned, and with zero required parameters the description does not say which identifier is mandatory or how sku/product_id/gtin interact.

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 and resource: generate the printable data carrier (QR content) of a twin, with two concrete output modes (GS1 Digital Link URL vs serialized twin URL fallback). It does not name or differentiate against near siblings such as build_gs1_digital_link or resolve_digital_link, so an agent must infer the boundary from naming alone.

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?

Gives clear conditional context: supply a valid GTIN for a GS1 Digital Link, omit it for the serialized fallback, and optionally pass allocation for channel-aware serialization. It offers no explicit when-not guidance or named alternatives for the closely-related Digital Link tools.

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