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. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent and non-open-world behavior, and the description meaningfully adds context beyond them: stateless with nothing stored, free, and an explicit 'not legal advice' disclaimer. It also discloses what the response embodies (validation results and missing fields), though it does not say how validation is performed or what limits apply.

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 action and artifact, and the content enumeration earns its place. Minor waste from 'Free' appearing twice ('Free and stateless' and 'free Cycle workspace') and a somewhat packed run-on list in the first sentence.

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, return values need not be explained, and the description still summarizes them. For an 8-parameter drafting tool the definition covers purpose, statelessness and disclaimers adequately; only the finer points of granularity/resolver semantics are left entirely to the schema.

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. The description only restates that the input is product data plus GTIN/UPI; it adds no meaning to granularity levels, base resolver usage, or the free-form product keys beyond what the schema says.

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 artifact: 'generate a draft EU Digital Product Passport (DPP) JSON document for a textile/fashion product', and enumerates the document's contents (UPI, Core-vocabulary fields, validation results, missing fields). It implies a drafting/preview role distinct from validate_dpp_document or create_dpp via the word 'draft', but never names a sibling, so differentiation is inferred rather than stated.

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?

Usage is implied by 'Use this tool to generate... from its data and GTIN', and the closing sentence hints that publishing is a separate step available with a workspace. There is no explicit when-not guidance and no named alternative for validating or publishing, leaving the agent to infer 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