Skip to main content
Glama

draft_dpp_document

Read-onlyIdempotent

Use this tool to generate a draft EU Digital Product Passport (DPP) JSON document for a textile/fashion product from its data and GTIN: unique product identifier (GS1 Digital Link UPI), Core-vocabulary fields, product data, validation results and the missing fields. Free and stateless (nothing is stored); publishing it at a resolvable UPI is offered with a free Cycle workspace. Not legal advice.

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

Input Schema

NameRequiredDescriptionDefault
lotNoLot for batch granularity.
baseNoOptional https resolver origin you control.
gtinNoGTIN/EAN of the product.
serialNoSerial for item granularity.
productYesProduct data with any keys: name, sku, description, brand, composition, country, supplier, care, compliance.
languageNoISO 639-1, default en.
granularityNo
product_groupNoDefault textiles.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, and the description reinforces rather than contradicts them by calling the tool free and stateless with nothing stored. It also adds genuinely non-obvious context: publishing requires a free Cycle workspace, and output is not legal advice. It does not cover size limits, error behavior, or why only the product param is required, but the added facts are substantive beyond 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?

The action and the output payload are front-loaded in the first clause, with behavioral caveats trailing. It is dense but each clause carries information; the "Not legal advice" disclaimer is the least load-bearing element but is short.

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, the description need not enumerate return values, yet it summarizes the draft contents and states the stateless, zero-cost, publish-with-workspace lifecycle. For an 8-parameter tool with a nested product object, the remaining gap is the relationship between the granularity enum and the lot/serial parameters, which the schema only partially resolves.

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 88%, so the schema already documents lot, base, gtin, serial, language, granularity, and product_group. The description only reinforces that GTIN and product data are inputs and does not explain how granularity interacts with lot/serial or what a resolver base does. Baseline 3 is appropriate where the schema does nearly all the work.

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?

"Generate a draft EU Digital Product Passport (DPP) JSON document for a textile/fashion product from its data and GTIN" is a specific verb plus resource plus domain, and it enumerates what the draft contains (UPI, Core-vocabulary fields, product data, validation results, missing fields). It never names or contrasts with siblings like create_dpp, map_product_to_dpp, or validate_dpp_document, so an agent must infer the boundary between drafting and those actions.

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

Usage Guidelines3/5

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

"Use this tool to generate..." frames the intended use and the note that publishing at a resolvable UPI requires a Cycle workspace implies a downstream step exists. However, there is no explicit when-not guidance and no named alternative (e.g., validate_dpp_document or create_dpp), so the routing decision is left implicit.

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