Skip to main content
Glama

TracePass DPP Compliance Assistant

List required passport fields

required_fields
Read-onlyIdempotent

Lists the data a passport must contain for a product category, with the article requiring each field, who may see it, how often it changes, and whether it usually comes from the maker or a supplier. Call it without group for a summary (counts by group), then with a group for the fields. 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. For inScope no, never say "not yet" or "yet"; for pending, name the planned act from data.planned. 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.

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": {
      "category": "<category>"
    },
    "name": "required_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNoTemplate group name. Omit for a summary; provide to list the fields.
localeNoLanguage for field labels and descriptions. Defaults to en.
subTypeNoBattery only: EV, LMT or industrial_gt_2kwh (an industrial battery over 2 kWh). Narrows the required fields to that battery type; an unknown value is refused with the allowed list.
categoryYesProduct category key, one of the listed values. Map the user's product to the closest key (paint → paints-coatings, an e-bike battery → battery). Never pass the user's own words. If none fits, there is no passport template for it: say so instead of calling.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Product category, e.g. battery."New value: +"Product category key, one of the listed values. Map the user's product to the closest key (paint → paints-coatings, an e-bike battery → battery). Never pass the user's own words. If none fits, there is no passport template for it: say so instead of calling."
    • addedInput schema / properties / category / enum
      Added value: +[
      +  "battery",
      +  "construction",
      +  "detergents",
      +  "electronics",
      +  "fmcg",
      +  "furniture",
      +  "jewelry",
      +  "packaging",
      +  "paints-coatings",
      +  "steel",
      +  "textile",
      +  "toys",
      +  "tyres"
      +]
    • removedInput schema / properties / category / maxLength
      Removed value: -100
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description does add real behavioral value by disclosing result states (summary vs. field list, not_covered, inScope no, pending with data.planned), but it never characterises the overall response shape or the disclaimer/citation fields it tells the agent to preserve.

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

Conciseness3/5

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

The purpose and call pattern are front-loaded and easy to find, but the back half is a long run of output-style mandates ('never say not yet', 'never rank or recommend vendors', 'never call yourself a consultant') that dilute the invocation guidance and partly exceed a tool definition's scope. It is organized but padded with rules of uneven relevance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry return-value meaning; it does name the per-field attributes and the key statuses, which is useful. However, it leaves the actual response structure and the disclaimer field unspecified, so an agent will meet an unanticipated envelope while being told to preserve fields it has not been shown.

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 schema already explains `group` (omit for summary), `locale`, `subType` (battery-only values) and `category` mapping. The description only restates the two-step `group` usage slightly, adding no format, default or validation detail beyond the schema. Baseline 3 is appropriate.

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 description opens with a specific verb and resource ('Lists the data a passport must contain for a product category') and enumerates the returned attributes (requiring article, visibility, change frequency, maker vs supplier source). That is far more specific than the title alone, though it never names or contrasts a sibling tool such as registry_guidance or scope_check.

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 a concrete call sequence: call without `group` for a summary of counts, then with a `group` to list fields, and it explains the not_covered outcome. What it lacks is any when-not-to-use guidance or an explicit alternative for adjacent questions (e.g., obligations vs. passport fields), and the parameter-mapping advice largely duplicates the schema.

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.