Skip to main content
Glama

TracePass DPP templates (regulatory schemas)

tracepass_templates
Read-onlyIdempotent

What 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

NameRequiredDescriptionDefault
argsNo
actionYes

Output Schema

NameRequiredDescriptionDefault
idNo
pageNo
errorNo
itemsNo
limitNo
totalNo
resultNo
messageNo
totalPagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • removedInput schema / properties / action / description
      Removed value: -"List all DPP category templates, or get one template by category."
    • removedInput schema / properties / args / description
      Removed value: -"Arguments for the chosen action; `category` is required for get, ignored for list."
    • changedInput schema / properties / args / properties / category / description
      Previous value: -"DPP category to fetch (required for get): battery | textile | electronics | construction | steel | detergents | paints-coatings | packaging | furniture | tyres | jewelry | toys | fmcg."New value: +"battery | textile | electronics | construction | steel | detergents | paints-coatings | packaging | furniture | tyres | jewelry | toys | fmcg."
    • removedOutput schema / properties / error / description
      Removed value: -"Machine-readable error code, when the API rejected the request."
    • removedOutput schema / properties / id / description
      Removed value: -"The resource's TracePass id, when the response is a single entity."
    • removedOutput schema / properties / items / description
      Removed value: -"The page of results, when the action is a list."
    • removedOutput schema / properties / limit / description
      Removed value: -"Page size (list actions)."
    • removedOutput schema / properties / message / description
      Removed value: -"Human-readable error or status detail, when present."
    • removedOutput schema / properties / page / description
      Removed value: -"Current page number (list actions)."
    • removedOutput schema / properties / result / description
      Removed value: -"Wraps a non-object response body (e.g. a QR code string)."
    • removedOutput schema / properties / total / description
      Removed value: -"Total matching records across all pages (list actions)."
    • removedOutput schema / properties / totalPages / description
      Removed value: -"Total number of pages (list actions)."
  2. Changed4 schema fields changed
    • removedOutput schema / properties / error / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / error / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / message / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / message / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. Changed4 schema fields changed
    • addedOutput schema / properties / error / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / error / type
      Removed value: -"string"
    • addedOutput schema / properties / message / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / message / type
      Removed value: -"string"
  4. Changed1 schema field changed
    • changedInput schema / properties / args / properties / category / description
      Previous value: -"DPP category to fetch (required for get): battery | textile | electronics | construction | steel | chemicals | packaging | furniture | tyres | jewelry | toys | fmcg."New value: +"DPP category to fetch (required for get): battery | textile | electronics | construction | steel | detergents | paints-coatings | packaging | furniture | tyres | jewelry | toys | fmcg."
  5. Changed6 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"List all DPP category templates, or get one template by category."
    • removedInput schema / properties / args / additionalProperties
      Removed value: -{}
    • changedInput schema / properties / args / description
      Previous value: -"Action-specific arguments — see the description for each action's shape."New value: +"Arguments for the chosen action; `category` is required for get, ignored for list."
    • addedInput schema / properties / args / properties
      Added value: +{
      +  "category": {
      +    "description": "DPP category to fetch (required for get): battery | textile | electronics | construction | steel | chemicals | packaging | furniture | tyres | jewelry | toys | fmcg.",
      +    "type": "string"
      +  }
      +}
    • removedInput schema / properties / args / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "error": {
      +      "description": "Machine-readable error code, when the API rejected the request.",
      +      "type": "string"
      +    },
      +    "id": {
      +      "description": "The resource's TracePass id, when the response is a single entity.",
      +      "type": "string"
      +    },
      +    "items": {
      +      "description": "The page of results, when the action is a list.",
      +      "items": {},
      +      "type": "array"
      +    },
      +    "limit": {
      +      "description": "Page size (list actions).",
      +      "type": "number"
      +    },
      +    "message": {
      +      "description": "Human-readable error or status detail, when present.",
      +      "type": "string"
      +    },
      +    "page": {
      +      "description": "Current page number (list actions).",
      +      "type": "number"
      +    },
      +    "result": {
      +      "description": "Wraps a non-object response body (e.g. a QR code string)."
      +    },
      +    "total": {
      +      "description": "Total matching records across all pages (list actions).",
      +      "type": "number"
      +    },
      +    "totalPages": {
      +      "description": "Total number of pages (list actions).",
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
  6. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/closed-world annotations, the description discloses the semantics that actually govern answers: `required` is a trap, `requiredBy[batteryCategory]` returns required | conditional | notApplicable, and only EV/LMT/industrial_gt_2kwh categories owe a passport under Art. 77(1) of Reg (EU) 2023/1542. It also points to an auxiliary resource (tracepass://reference/templates), which annotations cannot convey.

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?

Front-loaded purpose followed by a compact bulleted action list and a clearly signposted caveat block; every part is load-bearing. It loses a point for the final clause ('`conditional` fields, use data and the EV/LMT state-of-health split') which is compressed enough to be ambiguous, and for an inline resource URI that interrupts the battery warning.

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 an output schema present, the description need not document return values, yet it still usefully characterizes them, and given just two params it covers the invocation space fully. Completeness is slightly undercut by the garbled conditional-field guidance and by the dangling resource reference whose retrieval instructions are unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description compensates by mapping each action value to its args shape (`list` — {}, `get` — { category }) and by explaining the returned field attributes (key, label, dataType, REQUIRED flag, access level, bounds, mandating article). The `requiredBy[batteryCategory]` key is explained even though it never appears in the input schema.

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 opening line states a specific resource (compliant-passport field templates per category, per governing EU regulation) and enumerates both actions (list, get) with what each yields. An agent can tell it is a reference/schema lookup rather than a passport or product mutator, though it never names which sibling (e.g. tracepass_passport_fields, tracepass_scope) it supersedes.

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?

It gives clear positive usage guidance: consult before creating products/passports and to gap-check a draft, and it prescribes a mandatory ordering (SCOPE FIRST, then requiredBy, with `required` only as fallback). It stops short of explicit when-not or named-alternative routing, so it is strong context rather than full decision routing.

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.