Skip to main content
Glama

TracePass DPP Compliance Assistant

EU DPP Registry guidance

registry_guidance
Read-onlyIdempotent

Explains the EU DPP Registry and the technical side: registration in the registry, identifiers, QR and data carriers, data formats (JSON, HTML, data models) and standards, and where passport data is kept. Each point carries the date of its source. For who owes, keeps or may hand off a passport, use scope_check. 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": {
      "topic": "<topic>"
    },
    "name": "registry_guidance"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesThe topic to answer.
localeNoLanguage for the answer. Defaults to en.
categoryNoOptional category filter (e.g. battery) for category-specific guidance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context the annotations cannot convey: every point carries a source date, citations and a disclaimer line must survive, 'Planned, not law yet' / 'being re-checked' labels exist, and a not_covered result can occur with a pointer to the relevant article. What it does not do is describe result size or how multiple topics are returned.

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 scope statement and the scope_check pointer are correctly front-loaded, but the bulk of the text is answer-composition policy delivered as a run of short imperative sentences, with some near-duplication ('Never rank or recommend vendors. Never call this advice or yourself a consultant.'). It reads as a house-style rulebook appended to a tool description rather than tightly focused tool documentation.

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 no output schema, the description carries the burden of describing return content, and it does: per-point source dates, preserved citations and disclaimer, status labels, and the not_covered shape. Combined with a fully covered input schema, an agent has enough to invoke and present results correctly, though nothing is said about volume or whether requests can span multiple topics.

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 topic, locale and category are already documented in the schema with enums and a default. The description's topic list loosely mirrors the topic enum but adds no new meaning for locale or category, so the baseline 3 applies.

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 first sentence names a specific resource (EU DPP Registry) and enumerates the concrete subject areas covered: registration, identifiers, QR/data carriers, data formats, standards, where passport data is kept. It also explicitly distinguishes itself from the sibling scope_check, so an agent can route between them without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the exact alternative and the condition that selects it: 'For who owes, keeps or may hand off a passport, use scope_check.' It further states how to behave in edge outcomes (not_covered, inScope no, pending), which is explicit when/how guidance rather than implied context.

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.