Skip to main content
Glama

publish_product_passports

Idempotent

Use this tool when a brand wants Digital Product Passports (DPP), QR codes and a consumer page for its products, in one step. INPUT: products (name, sku, gtin, composition, country of manufacture, care, materials... any shape, same as create_product_twin) and optionally units per product (how many physical units will carry a serial QR). For each product it creates the live twin in Cycle, publishes the versioned passport when the data is complete and the GTIN is valid (otherwise a 'preparatory' passport that lists what is missing) and returns the twin URL, the passport URL and a QR (SVG link ready to print). Free up to 1,000,000 physical units per connected free workspace (total, not monthly). Brand and product data are stored in Cycle under the connected brand. Not an official certification; EU registry submission is separate.

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": {
      "products": "<products>"
    },
    "name": "publish_product_passports"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsNoOptional {sku_or_name: units} map of serialized units to reserve per product
productsYes
idempotency_keyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false and idempotentHint=true), the description discloses a lot: the live twin is created, a versioned passport is published when data is complete and the GTIN is valid, otherwise a preparatory passport listing missing fields is returned, along with the three outputs. It also states quota limits (1,000,000 free physical units per connected workspace, total, not monthly), where brand and product data is stored, and the caveat that this is not an official certification and that EU registry submission is handled separately.

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?

It is a single dense paragraph, but it is front-loaded with the use condition, then an explicit 'INPUT:' section, then the processing logic, then limits and caveats. Every sentence carries information, though the run-on structure and the parenthetical caveats make it heavier than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter tool with nested free-form product objects, an output schema and annotations present, the description covers the missing pieces: input flexibility, the conditional passport behavior, upstream quota constraints, data storage location, and the separate EU registry step. It explains the return values anyway, even though an output schema exists, which is harmless surplus.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, so the description has to fill the gap. It does: products is described as accepting flexible shapes with example fields (name, sku, gtin, composition, country of manufacture, care, materials) and as matching create_product_twin, and units is explained as a serialized-unit count map per product. The idempotency_key parameter is not explained in the description, though idempotentHint=true hints at its purpose.

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 specific operations and resources: it creates a live product twin, publishes a versioned passport, and returns the twin URL, passport URL and print-ready QR SVG. It also implicitly distinguishes itself from create_product_twin by covering the whole flow 'in one step', so an agent can tell it apart from the plain twin-creation sibling without reading either schema.

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 opening sentence gives an explicit use condition: brands wanting DPPs, QR codes and a consumer page for their products in one step. It also explains the fallback path when data is incomplete or the GTIN is invalid, resulting in a preparatory passport. However, it never excludes cases or names the sibling tools to use instead (for example, publishing an existing draft via map_product_to_dpp or create_dpp), so the agent has to infer that routing.

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