Skip to main content
Glama

Dutch licence plate check (free)

nl_vehicle_basic
Read-onlyIdempotent

Free. Use when the user gives a Dutch licence plate or asks about a specific car in the Netherlands: make, model, age, fuel, Euro class, APK (MOT) expiry, insurance, open recall, RDW odometer verdict and a risk level. Source: RDW.

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": {
      "licence_plate": "<licence_plate>"
    },
    "name": "nl_vehicle_basic"
  }
}

Input Schema

NameRequiredDescriptionDefault
licence_plateYesDutch licence plate, e.g. GT-722-F

Output Schema

NameRequiredDescriptionDefault
apkNoAPK expiry
sourceNoSources to cite
recallsNoOpen recalls
see_urlNoFactline page for this plate
vehicleNoMake, model, colour, first registration

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "apk": {
      +      "description": "APK expiry"
      +    },
      +    "recalls": {
      +      "description": "Open recalls"
      +    },
      +    "see_url": {
      +      "description": "Factline page for this plate"
      +    },
      +    "source": {
      +      "description": "Sources to cite"
      +    },
      +    "vehicle": {
      +      "description": "Make, model, colour, first registration"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added
  3. Removed
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real value beyond that: it identifies RDW as the authoritative source and states the tool is free, which matters because several siblings are paid. Rate limits or quotas are not mentioned.

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

Conciseness5/5

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

Two dense sentences, front-loaded with the cost signal and the trigger condition, followed by an enumeration of returned fields. No filler sentences; every clause carries information.

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 explain return structure, yet enumerating the covered fields helps the agent match user intent to this tool versus the paid report. Source attribution and cost are included. Only the sibling-routing guidance is thin.

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?

Only one parameter with 100% schema coverage, and the schema itself supplies an example format ('GT-722-F'). The description adds no syntax or validation detail beyond that, so the baseline 3 for a fully documented single parameter 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?

States a concrete resource (Dutch licence plate lookup) and enumerates the exact data returned: make, model, age, fuel, Euro class, APK expiry, insurance, recall, odometer verdict, risk level. An agent knows precisely what this returns. It does not explicitly contrast with siblings like nl_vehicle_report or buy_full_vehicle_report, relying instead on 'Free' to imply the difference.

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?

Gives a clear triggering condition: 'Use when the user gives a Dutch licence plate or asks about a specific car in the Netherlands.' The 'Free' qualifier implicitly separates it from the paid report siblings, but the description never names an alternative tool or states when to escalate to one.

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.

Resources