Skip to main content
Glama

Nl Vehicle By Plate

nl_vehicle_by_plate
Read-onlyIdempotent

Look up a Dutch licence plate (kenteken) in the vehicle authority register: make, model, vehicle type, colour, first registration date, age, fuel, euro class, APK (MOT) expiry and whether it is valid, insured flag, open recall flag, odometer verdict (consistent / suspect) and an overall risk level. Describes the VEHICLE only; no owner or personal data is requested or returned. Example: {"licence_plate":"GT722F"} -> Mazda CX-3, APK valid to 2027-08-14. An unregistered plate returns found:false. Returns source and data_as_of (retrieval date).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
licence_plateYesDutch licence plate, with or without dashes, e.g. "GT-722-F" or "GT722F"

Output Schema

NameRequiredDescriptionDefault
fuelNo
makeNo
foundNo
modelNo
plateNo
colourNo
sourceNo
cite_asNo
insuredNo
summaryNo
age_yearsNo
apk_validNo
apk_expiryNo
data_as_ofNo
euro_classNo
risk_levelNo
open_recallNo
vehicle_typeNo
provenance_noteNo
first_registeredNo
odometer_verdictNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description discloses the negative case (unregistered plate returns found:false), the privacy scope, and provenance/currency signals (source, data_as_of). That is meaningful operational context an agent needs before calling and before trusting the result.

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?

It is a single front-loaded paragraph with a concrete example and no filler; every clause communicates capability, privacy scope, or the empty-result behavior. The long enumeration of returned fields is somewhat redundant given an output schema exists, which keeps it from a 5.

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

Completeness5/5

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

For a one-parameter lookup with annotations and an output schema, the description covers everything an agent needs: what is queried, what is returned at a high level, the not-found case, privacy limits, and data freshness. Nothing material is missing.

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?

With one parameter at 100% schema coverage, the schema already documents the licence plate and even the dash/no-dash flexibility. The description's example ({"licence_plate":"GT722F"}) reinforces format and expected output but adds no meaning the schema lacks, so 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?

"Look up a Dutch licence plate (kenteken) in the vehicle authority register" gives a concrete verb and resource, and the enumeration of returned attributes (make, model, APK expiry, odometer verdict, risk level) makes the tool's scope unmistakable. An agent can distinguish this from register/company lookups or a recall tool without inspecting the schema.

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 states the use case plainly (single Dutch plate lookup) and clarifies the privacy boundary — vehicle only, no owner or personal data requested or returned — which tells the agent when this is the appropriate call. It does not name an explicit alternative or exclusion condition, but the domain is narrow enough that context is clear.

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.