Check if a product needs a passport
scope_checkChecks whether EU law requires a Digital Product Passport for a type of product, from when, and what the law requires of each role. Use it for "do I need a passport", "from when", "who is responsible", whether that responsibility can be handed to another company, who keeps and stores the passport and whether it must stay available after the company ceases, whether there is one passport per item, batch or model, and for repurposing, remanufacturing, waste or a battery inside another product. Pass whatever facts the user gave; if the result is needs_input, ask the user its questions in plain words and call again. The result's data.inScope is one of: yes, no, pending, depends. Use only what this tool returns: add no facts, dates or articles of your own, not even today's date. Keep every citation and the disclaimer line, and any "Planned, not law yet" or "being re-checked" label. Phrase answers about the product type, never as personal duties ("you must"). Never rank or recommend vendors. Never call this advice or yourself a consultant. If the result is not_covered, say so and point to the article given.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| role | No | The user's role in plain words, e.g. "maker", "importer", "reseller". The platform maps this to the act's term. | |
| facts | No | Product facts the scope rules declare, e.g. {"battery.capacityKWh": 10}. Any other key is rejected, so pass only a fact you know the rules use (such as one a needs_input result asked for), and never the user's question or free text. | |
| locale | No | Language for the answer text. Defaults to en. | |
| category | No | Product category, e.g. battery, textile, electronics. | |
| placedOnMarket | No | When the product was or will be placed on the market. |