QRStuff MCP Server

Create Digital Product Passport

create_digital_product_passport

Use this when the user wants a GS1 Digital Link QR code or a Digital Product Passport for a product: a QR code carrying the product's GTIN that opens a page with product details, traceability, certifications or links. Needs a GTIN and product details. Creates a dynamic code in the account. Do not use it for ordinary web-link QR codes.

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": {
      "gtin": "<gtin>",
      "product": "<product>"
    },
    "name": "create_digital_product_passport"
  }
}

Input Schema

Name	Required	Description	Default
`gtin`	Yes	The product's GS1 GTIN, 8, 12, 13 or 14 digits.
`product`	Yes	Product details such as name, brand, description and image. Call `list_qr_data_types` with data_type DPP_GS1 for the exact keys.
`qr_name`	No	Optional name for the QR code in the dashboard.	Digital Product Passport
`passport`	No	Optional Digital Product Passport details such as materials, certifications and care or recycling information.
`traceability`	No	Optional traceability details such as batch, origin and manufacturing dates.
`resolver_links`	No	Optional extra links for the product page, each with a label and URL.
`custom_attributes`	No	Optional extra product attributes as name and value pairs.
`scan_authenticity_enabled`	No	true to turn on scan authenticity checks for this code.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly=false, idempotent=false, openWorld=true and destructive=false, so the safety profile is covered. The description adds genuinely new context: it creates a *dynamic* code stored in the account, meaning the destination content can change after creation, which explains the non-idempotent/dynamic distinction. It does not mention permissions, quotas, or failure modes for missing/invalid GTINs.

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?

Three tight sentences: what it produces, what it needs, what it is not. The use-case trigger is front-loaded and no sentence is filler.

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?

With an output schema present and 100% schema coverage, the description need not explain return values, and it covers the key concept (dynamic GTIN-based passport code) and required inputs. It could say more about how the optional passport/traceability/resolver_links blocks change the generated page, but nothing essential for correct invocation is missing.

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 already 100%, so the baseline would be 3. The description raises it by flagging the two required inputs (gtin, product) and by pointing the agent to list_qr_data_types with data_type DPP_GS1 for the exact keys of the free-form product object — useful guidance that the schema itself only partly conveys.

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?

States a specific verb and resource ('Create Digital Product Passport' / GS1 Digital Link QR carrying a GTIN that resolves to a product page) and immediately distinguishes it from ordinary web-link QR codes. An agent can tell this apart from generate_qr_code or create_static_qr_code without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('when the user wants a GS1 Digital Link QR code or a Digital Product Passport'), the prerequisites ('Needs a GTIN and product details'), and an explicit exclusion ('Do not use it for ordinary web-link QR codes'). That is a full when/when-not statement, which is rare.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All QRStuff MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?