Skip to main content
Glama

validate_dpp_readiness

Read-only

Use this tool when a company needs to know whether its product catalogue is READY for the EU Digital Product Passport (DPP/ESPR): pass an array of products (any reasonable JSON shape: name, sku, description, brand, composition/material, country of origin, supplier, care instructions...) and get a rule-based readiness score 0-100 per product plus the exact missing fields, and an aggregate with the single field that unlocks the most products. INPUT: array of product objects (flexible keys). OUTPUT: per-product score, ready flag, missing field labels; aggregate with top_missing_fields and unlock_hint. Deterministic internal data-completeness rules; not an official textile schema or certification. Up to 200 products per call. No account needed.

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": "validate_dpp_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
productsNoProducts to validate. Flexible keys accepted: name/title, sku, description, brand/vendor, composition/material/fabric, country/origin/manufacturing_country, supplier, care/care_instructions, compliance, certifications.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the real burden and does so: deterministic internal rules, explicitly not an official textile schema or certification, a 200-product cap, and no account required. The disclaimer about non-certification is exactly the kind of caveat an agent needs to relay to a user.

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 use case, then cleanly partitioned into INPUT and OUTPUT segments, which makes it scannable. It is a bit dense and run-on, and the flexible-key list is duplicated against the schema, but no sentence is wasted.

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

Completeness5/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 values need not be explained, yet the description still names score, ready flag, missing field labels, top_missing_fields and unlock_hint, plus the batch limit and the non-certification caveat. Nothing an agent needs to call it correctly is missing.

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 coverage is 100% and the description's list of acceptable keys (name, sku, brand, composition, country of origin, supplier, care) largely restates the schema's own enumeration of flexible aliases. Baseline 3 applies since the schema already does the heavy lifting for this single parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: rule-based readiness scoring of a product catalogue for EU DPP/ESPR, with per-product scores and aggregate unlock hints. This is clearly distinguishable from document-level siblings like validate_dpp_document and check_dpp_requirements.

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?

Opens with an explicit trigger condition ('when a company needs to know whether its product catalogue is READY for the EU DPP'), which gives strong when-to-use context. It does not explicitly exclude the document-validation or requirements-check siblings, leaving the catalogue-level vs document-level boundary to be inferred.

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