Skip to main content
Glama

check_dpp_requirements

Read-only

Use this tool when a company or user asks WHAT the EU Digital Product Passport (DPP) requires, WHEN it becomes mandatory, which ESPR/AGEC/French milestones apply to textile or fashion products, or whether the DPP is already obligatory. Returns the regulatory reference timeline with its recorded review status, the mandatory data fields a textile DPP needs, and honest notes on what is in force vs pending delegated acts. Deterministic, no account needed. Informational, not legal advice.

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

Input Schema

NameRequiredDescriptionDefault
sectorNoSupported sector: textile or fashion. Other sectors return unsupported_sector rather than textile rules.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds meaningful context beyond them: deterministic output, no account required, honest disclosure of what is in force versus pending delegated acts, and an explicit "informational, not legal advice" caveat. What it does not cover is pagination/formatting or how the recorded review status should be interpreted.

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?

Well front-loaded: the trigger condition leads, followed by return contents and caveats. The first sentence is heavily compounded with multiple clauses (WHAT/WHEN/which milestones/whether obligatory), which slightly hurts scannability, but no sentence is filler.

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 simple one-optional-parameter read tool with an output schema, the description covers purpose, triggers, scope limits, and behavioral caveats. Minor gaps: it does not note that sector is optional/defaulted or point to the natural next step (e.g., create_dpp or map_product_to_dpp) after requirements are known.

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 single sector parameter is fully documented in the schema, including the unsupported_sector fallback. The description reinforces the textile/fashion scope but adds no syntax, default, or optionality detail beyond the schema, so the baseline 3 applies.

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 set: it answers WHAT the EU DPP requires, WHEN it becomes mandatory, which ESPR/AGEC/French milestones apply, and whether it is already obligatory. This informational/regulatory-lookup role is clearly separable from siblings like create_dpp, validate_dpp_readiness, or map_product_to_dpp.

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 opening clause gives explicit trigger conditions ("Use this tool when a company or user asks WHAT... WHEN... whether the DPP is already obligatory") and scoping to textile or fashion. It stops short of naming a sibling alternative or a when-not-to-use case, so it falls one step below the top band.

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