Skip to main content
Glama

validate_dpp_document

Read-onlyIdempotent

Use this tool to check a Digital Product Passport JSON document before publishing or registering it: required Core fields, UPI format, granularity, status, dates, language and content-specification release URIs, plus the status of the official EU JSON Schema (honestly reported as unavailable until published). No account needed.

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": {
      "document": "<document>"
    },
    "name": "validate_dpp_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentYesThe DPP JSON document.
product_groupNoProduct group, default 'textiles'.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so the safety profile is covered. The description adds genuinely non-redundant context: no account/authentication is required, and the EU JSON Schema status is 'honestly reported as unavailable until published', which pre-empts a confusing result. It does not say what happens on failure or how findings are aggregated, keeping it below 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?

A single front-loaded sentence that opens with the action and then enumerates scope. The list is dense but each item is a real validation rule rather than filler; a slightly tighter phrasing of the schema caveat would improve it.

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?

An output schema exists, so return-value details are rightly omitted, and annotations carry the safety profile. Combined with the auth note and the schema-availability caveat, an agent has enough to call this correctly; only the absence of explicit sibling routing leaves a small gap.

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 100%, so both parameters are already documented, and the description adds little beyond restating that a DPP JSON document is the input. The 'product_group' parameter, including its default of 'textiles', is never mentioned in the description, so no extra semantics are contributed.

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 ('check') and resource ('Digital Product Passport JSON document') and enumerates the exact validation dimensions: Core fields, UPI format, granularity, status, dates, language, content-specification release URIs. It implicitly separates itself from the broader readiness-checking sibling by scoping to a document instance, but it never names an alternative, so differentiation is inferential rather than explicit.

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

Usage Guidelines4/5

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

Gives a clear usage context: run it 'before publishing or registering' a DPP document, which tells the agent where in a workflow it belongs. It stops short of stating when not to use it or pointing at validate_dpp_readiness / check_dpp_requirements for pre-document checks.

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