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

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write/safety profile is partly covered. The description adds genuinely new behavioral facts: a valid GTIN is mandatory, specific authorisation scopes are required, the response carries real UPI, content hash, version, environment and separate provisional/official validation states, and the tool does not touch the EU Registry or assert certification. What is missing is failure behaviour (e.g. what happens on duplicate publish) although idempotency_key hints at it.

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 dense sentences, front-loaded with the action and then the precondition, return shape, and scope boundary. Nearly every clause earns its place, with only the return-value enumeration being partially redundant given an output schema exists.

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?

The tool has annotations and an output schema, so return values and safety profile are partly covered and the description usefully flags which return fields matter. But for a 7-parameter publish operation with zero schema coverage and no required parameters declared, the description leaves too much of the invocation surface (granularity choice, idempotency semantics, identifier combinations) unexplained.

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

Parameters2/5

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

Schema description coverage is 0% across 7 parameters, so the description carries the full burden and does not meet it. It explains only that gtin must be valid; it says nothing about granularity (model/batch/item), product_id, sku, lot, serial, or what idempotency_key does. Six of seven parameters are undocumented in both schema and description.

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: publishes the canonical versioned passport of a product in the organisation, and names the identity requirement (valid GTIN). It is clear what the tool does and what it deliberately does not do (EU Registry submission, certification claims), though it never explicitly contrasts itself with the close sibling publish_product_passports.

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?

Provides implied usage context ('in your organisation', valid GTIN required, needs dpp:write or legacy create scope) and a clear negative boundary ('never submits to the EU Registry or claims certification'). However, it gives no explicit when-to-use vs when-not guidance relative to siblings such as publish_product_passports, draft_dpp_document or validate_dpp_readiness, so an agent must infer selection.

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