Skip to main content
Glama

dpp_readiness_check

Read-only

Free informational EU Digital Product Passport readiness questionnaire; this cannot issue a passport or certify compliance. Returns a 0-100 score, gaps, and the dated obligation for the product category (battery passport is law from 18 Feb 2027; other categories are ESPR targets). Not legal advice.

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": {
      "category": "<category>"
    },
    "name": "dpp_readiness_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesbattery_passport: EV, LMT (e-bike, e-scooter) or industrial battery over 2 kWh; battery_other: Other battery (portable, SLI, industrial up to 2 kWh); textiles: Textiles, apparel or footwear; iron_steel: Iron and steel; aluminium: Aluminium; tyres: Tyres; furniture: Furniture; mattresses: Mattresses; electronics: Electronics and ICT; toys: Toys; construction: Construction products; detergents: Detergents and cleaning products; other: Something else
data_hostNoYou have a public web location where product data could be published behind a QR code.
footprintNoYou have carbon or environmental footprint data for the product.
unique_idNoEach product (or model or batch) has a unique identifier, such as a GS1 GTIN with serial.
data_ownerNoA named person owns product compliance data.
market_roleNoYou know who places the product on the EU market (you, an importer or an EU representative).
sells_in_euNoSold into the EU directly or via an importer. Default true.
supplier_dataNoYou can get material and substance data from your suppliers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds genuinely useful context beyond that: the tool is free and informational, cannot certify, and is not legal advice. However, it does not say how the boolean inputs are weighted or what happens when optional answers are omitted.

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?

Three dense sentences with the core scope and the non-certification caveat front-loaded, and no filler. The parenthetical date detail is compact and earns its place by explaining the output.

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?

With no output schema, the description takes on the job of describing returns and does so concretely (score, gaps, dated obligation). Combined with annotations covering safety and a fully documented schema, an agent has nearly everything needed; only the scoring mechanics remain unspecified.

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%, including per-enum-value explanations for category and a default noted for sells_in_eu, so the schema carries the parameter burden. The description adds only the meaning of the returned obligation date (battery passport law from 18 Feb 2027 vs ESPR targets), not any semantics for the eight input parameters.

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 names a specific artifact (an EU Digital Product Passport readiness questionnaire) and states what it produces (a 0-100 score, gaps, and a dated obligation). It also draws a clear line against verification tools by saying it 'cannot issue a passport or certify compliance', though it never names the sibling tools it is being distinguished from.

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?

The intended use is implied by 'readiness questionnaire' and by the explicit exclusion of passport issuance and compliance certification, which helps separate it from verify/verify_attestation. There is no explicit when-to-use or when-not statement, no prerequisites, and no named alternative to route to.

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.