TracePass DPP templates (regulatory schemas)
tracepass_templatesWhat a COMPLIANT passport must contain per category, per the governing EU regulation. Read-only reference data; use it to advise on requirements before creating products/passports and to gap-check a draft.
Actions (pass via action; {…} is the args object):
list — {}. All 13 categories with counts and governing regulation.
get — { category }. Every field: key, label, dataType, REQUIRED flag, access level, options, bounds and, where known, the mandating article.
BATTERY — required alone is the wrong answer. SCOPE FIRST: only EV, LMT and industrial_gt_2kwh batteries owe a passport (Art. 77(1), Reg (EU) 2023/1542); for portable, SLI or industrial_lte_2kwh NO field is required — say it is out of scope and list no mandatory fields. Then use requiredBy[batteryCategory] (required | conditional | notApplicable), and required only as a fallback; skipping the scope step invents an obligation the Regulation does not impose. conditional fields, use data and the EV/LMT state-of-health split: resource tracepass://reference/templates.
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": {
"action": "<action>"
},
"name": "tracepass_templates"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| args | No | ||
| action | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | ||
| page | No | ||
| error | No | ||
| items | No | ||
| limit | No | ||
| total | No | ||
| result | No | ||
| message | No | ||
| totalPages | No |