Skip to main content
Glama

TracePass DPP Compliance Assistant

What changed in EU passport law

what_changed
Read-onlyIdempotent

Reports changes in EU passport law and standards for the user's categories since a date (default: since they last asked). Use it for "what's new" or "has X been adopted". Items marked "Planned, not law yet" are upcoming obligations, not yet in force. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "what_changed"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoISO date to look back from. Defaults to the date this account last called what_changed (first time: 90 days ago).
localeNoLanguage for summaries. Defaults to en.
categoriesNoProduct categories to filter by. Defaults to the saved profile categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only cover the read-only/idempotent safety profile, and the description adds substantial behavior beyond that: the default 'since' resolves to the account's last call (90 days on first use), results may carry 'Planned, not law yet' and 'being re-checked' labels, and there are not_covered, inScope-no and pending result states with prescribed handling. That is real disclosure about what the output means, not just what the tool does.

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?

Purpose and default window are front-loaded before the response rules, and every sentence carries a distinct constraint (citation retention, no personal-duty phrasing, no vendor ranking, not_covered handling). The rule list is dense but not padded, though it reads as a policy block rather than a structured summary.

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 does the necessary work of explaining result labels and edge states, which an agent could not otherwise infer. It only gestures at the payload structure (one reference to data.planned) and says nothing about result size or volume, so the return shape is not fully covered.

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 all three parameters (since, locale, categories) plus the locale enum and profile defaults are already documented in the schema. The description's mention of a date default and the user's categories restates rather than extends that; baseline 3 applies.

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 states a specific verb and resource ('Reports changes in EU passport law and standards for the user's categories since a date') and even supplies the trigger phrasings ('what's new', 'has X been adopted'). It is clearly distinguishable from static-guidance siblings, though it never names an alternative tool to route away from.

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 when-to-use condition ('what's new' or 'has X been adopted') and a default time window tied to prior usage. It stops short of stating when not to use it or which sibling to pick instead, so routing between this and registry_guidance or scope_check is left implicit.

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.