Skip to main content
Glama
Sign In

Aeroz

by io.aeroz
OverviewDiscussionsAdmin

Passport readiness

dpp_readiness
Read-onlyIdempotent

Assess how ready a product category is for an EU Digital Product Passport, against the delegated act that applies to it. Returns the required data fields, which are present, and which are missing. For batteries (category "batteries", or "lmt" / "ev" / "industrial" / "stationary") the assessment is against the Commission's 71 numbered data points: score, missing, not-required-yet, awaiting first reading and go_live_ready per passport; pass unit_id for one battery passport. IMPORTANT: this is a readiness signal, not a legal compliance determination — never report its output as confirmation that a product is compliant.

Input Schema

NameRequiredDescriptionDefault
unit_idNoOptional: one chain unit (cun_…) holding a battery passport, for its own readiness.
categoryYesProduct group, e.g. "batteries", "textiles", "iron_steel", "furniture", "tyres", "aluminium"; or a battery category "lmt", "ev", "industrial", "stationary".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Product group, e.g. \"batteries\", \"textiles\", \"iron_steel\", \"furniture\", \"tyres\", \"aluminium\"."New value: +"Product group, e.g. \"batteries\", \"textiles\", \"iron_steel\", \"furniture\", \"tyres\", \"aluminium\"; or a battery category \"lmt\", \"ev\", \"industrial\", \"stationary\"."
    • addedInput schema / properties / unit_id
      Added value: +{
+  "description": "Optional: one chain unit (cun_…) holding a battery passport, for its own readiness.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds useful behavioral context: it describes returned readiness fields, the 71 battery data points, battery-category handling, and an important legal-interpretation caveat.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the main purpose, then quickly covers return content, battery-specific behavior, and the critical caveat. Every sentence carries useful information and there is no redundant wording.

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?

Although there is no output schema, the description names the key returned fields and explains the battery-specific assessment structure. Combined with annotations that cover safety and idempotency, it provides enough information for an agent to invoke the tool correctly and interpret its output cautiously.

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 in the schema. The description reinforces the battery category names and the unit_id use case for a single battery passport, but it adds little semantic detail beyond what the schema already provides.

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?

The description states a specific verb and resource: assess readiness of a product category for an EU Digital Product Passport against the applicable delegated act. It also distinguishes the tool from sibling passport tools by explaining that it returns required, present, and missing data fields rather than passport contents or verification results.

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 description gives clear context for use, including battery-specific categories and the condition for passing unit_id for a single battery passport. It also includes a critical usage caveat that output is a readiness signal, not a legal compliance determination, though it does not explicitly name which sibling to use instead for compliance-style checks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Aeroz toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources