Skip to main content
Glama

dpp_payload_validator

Read-onlyIdempotent

[Deterministic ESPR & DPP validation. Pure calculation, read-only, side-effect free]. Audits Digital Product Passport (DPP) payloads under EU ESPR Regulation 2024/1781, validates GS1 Digital Link URIs, verifies REACH Art. 33 Candidate List SVHC thresholds (>0.1% w/w), and scores circularity & repairability index. Usage: Use this tool to validate product passport schemas for batteries, textiles, electronics, and construction products before EU market entry. Returns: JSON object with { isValidDpp: boolean, digitalLinkValidation: object, svhcCompliance: object, circularityMetrics: object, carbonMetrics: object, esprComplianceStatus: string }.

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": {
      "productCategory": "<productCategory>",
      "gtin": "<gtin>"
    },
    "name": "dpp_payload_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
gtinYesGTIN-13 or GTIN-14 barcode identifier
serialNumberNoUnique item serial number
digitalLinkUriNoGS1 Digital Link URI string
productCategoryYesTarget product sector under ESPR / Battery Regulation
repairabilityScoreNoRepairability score from 0.0 to 10.0
carbonFootprintKgCo2eNoProduct lifecycle carbon footprint (kg CO2e)
expectedLifespanYearsNoExpected functional lifespan in years
recycledContentPercentageNoCertified recycled content percentage (0-100)
substancesOfVeryHighConcernNoREACH Candidate List SVHC substances
recycledCertificationStandardNoCertification scheme (e.g. GRS, ISCC PLUS, RecyClass)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint and idempotentHint, and the bracketed preamble ('pure calculation, read-only, side-effect free') largely restates them. What it genuinely adds is the determinism guarantee and the prosaic enumeration of returned objects, which helps since no output schema exists. It says nothing about failure behavior for malformed payloads, unknown GTINs, or unsupported category/regulation combinations.

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 bracketed summary, Usage, and Returns lines are a clean front-loaded structure with no filler prose. Minor waste in the opening 'pure calculation, read-only, side-effect free' triple, which duplicates the supplied annotations rather than adding new information.

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?

For a 10-parameter, no-output-schema compliance tool, the definition does real work: it names the governing regulation, lists the return object's fields, and anchors the SVHC threshold. It is not fully complete, since an agent still cannot predict what happens with an invalid GS1 Digital Link or how partial validation results are reported.

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 the baseline is 3 regardless of the description. The description adds one substantive piece of semantics beyond the schema: the >0.1% w/w SVHC threshold that gives meaning to concentrationPercentWeight. The other nine parameters, including repairabilityScore and recycledCertificationStandard, get no interpretation beyond their schema text.

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?

The description uses specific verbs and resources: it audits DPP payloads under EU ESPR Regulation 2024/1781, validates GS1 Digital Link URIs, verifies REACH Art. 33 SVHC thresholds, and scores circularity/repairability. That is far more than a restated name. It stops short of 5 because it never distinguishes itself from the sibling audits (construction_materials_cpr_audit, green_claims_substantiation_audit), which could plausibly be reached for the same EU compliance check.

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?

The 'Usage:' line gives a concrete trigger: validate passport schemas for batteries, textiles, electronics, and construction products before EU market entry, which maps directly to the productCategory enum. There is no guidance on when not to use it, no mention of the sibling compliance tools as alternatives, and no stated prerequisites such as needing a resolved GTIN.

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