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 100,000 units per brand. 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. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false), the description discloses the concrete write effects: which resources are created, the versioned-publish behavior, the 'preparatory' fallback when data or GTIN is incomplete, data residency ('stored in Cycle under the connected brand'), a quota ('free up to 100,000 units per brand'), and a liability boundary (not an official certification). These are exactly the side-effect and constraint details an agent cannot infer from the annotation flags.

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?

The description is front-loaded with the activation condition, then moves through input, behavior, quota, and caveats in a logical order. It is dense but every sentence carries information; the only minor slack is the informal 'any shape' phrasing and long compound sentences that could be split for scannability.

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 batch, nested-object write tool with an output schema, the description covers inputs, side effects, quota, and the incomplete-data branch, which is enough to invoke it correctly. Remaining gaps are the unmentioned `idempotency_key` and no statement about partial-failure semantics when some of the up-to-200 products are invalid, though the 'preparatory' passport clause partially addresses that.

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 coverage is only 33%, so the description has to carry meaning, and it does for the dominant parameter by enumerating expected product fields (name, sku, gtin, composition, country of manufacture, care, materials) and clarifying that shape is flexible and matches create_product_twin. It also explains `units` as 'how many physical units will carry a serial QR', reinforcing the schema text. The `idempotency_key` parameter is left completely unaddressed in both schema description and prose, so the compensation is substantial but incomplete.

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 gives a specific verb chain and resource: creates the twin, publishes a versioned passport, returns twin/passport URLs and a printable QR. The phrase 'in one step' implicitly separates it from single-step siblings such as create_product_twin or create_dpp, and it explicitly anchors the input shape to create_product_twin. It stops short of naming the sibling it replaces when an agent already has a twin, so it is clear but not fully differentiated.

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 opens with an explicit activation condition ('Use this tool when a brand wants DPP, QR codes and a consumer page ... in one step'), which is a real when-to-use rule. It also sketches the outcome branches (complete + valid GTIN vs. 'preparatory' passport) and a scope exclusion ('EU registry submission is separate'). No alternative tool is named as the fallback path, so exclusion guidance is present but alternatives are not.

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