Skip to main content
Glama

create_dpp

Use this tool to publish the canonical versioned passport of a product in your organisation. A valid GTIN is required. Returns its real UPI, content hash, version, environment and separate provisional/official validation states. It never submits to the EU Registry or claims certification. Requires dpp:write or legacy create scope.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_dpp"
  }
}

Input Schema

NameRequiredDescriptionDefault
lotNo
skuNo
gtinNo
serialNo
product_idNo
granularityNo
idempotency_keyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / granularity
      Added value: +{
      +  "enum": [
      +    "model",
      +    "batch",
      +    "item"
      +  ]
      +}
    • addedInput schema / properties / gtin
      Added value: +{
      +  "maxLength": 14,
      +  "type": "string"
      +}
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "maxLength": 120,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / lot
      Added value: +{
      +  "maxLength": 20,
      +  "type": "string"
      +}
    • addedInput schema / properties / product_id / maxLength
      Added value: +120
    • addedInput schema / properties / serial
      Added value: +{
      +  "maxLength": 20,
      +  "type": "string"
      +}
    • addedInput schema / properties / sku / maxLength
      Added value: +120
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "anyOf": [
      +    {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    {
      +      "required": [
      +        "created"
      +      ]
      +    }
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses the auth scope needed (dpp:write or legacy create) and the important negative boundary that it never submits to the EU Registry or claims certification. It also previews the return payload (UPI, content hash, version, environment, provisional/official states). It doesn't say what happens on repeated publishes or how idempotency interacts, which keeps it short of a 5.

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?

Four compact sentences with no wasted clauses, and the core action is front-loaded before the caveats and auth requirement. The opening "Use this tool to" is mild filler that directly introducing "publish" would remove. The return-field list is dense but earns its place.

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

Completeness3/5

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

An output schema exists, so the description needn't fully explain return values, yet it does sketch them, and the auth, GTIN and registry caveats cover the main behavioral questions. The gap is qualifying the remaining inputs, because nothing explains lot, sku, serial, product_id, granularity or idempotency_key. For a 7-parameter write tool that gap is material.

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

Parameters5/5

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

Schema coverage is 0% across 7 parameters, so the description carries the full burden. It compensates by stating that a valid GTIN is required and by naming the meaningful return fields (UPI, hash, version, environment, validation states). That turns an otherwise undocumented schema into a usable one, so the parameter semantics dimension rates highly.

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 resource: "publish the canonical versioned passport of a product in your organisation." That distinguishes it from the drafting and validation siblings (draft_dpp_document, validate_dpp_document) without naming them, and the EU Registry caveat further narrows the scope. It stops short of an explicit sibling comparison, so it's clear rather than exemplary.

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 publish..." gives an implied when, and the GTIN requirement plus the dpp:write scope are stated prerequisites. However, there is no guidance on when to pick this over draft_dpp_document or map_product_to_dpp, and no statement about what to do when a passport already exists. Usage is inferable but not routed for the agent.

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