Skip to main content
Glama

Free vehicle check by registration

free_vehicle_check
Read-onlyIdempotent

Free check of a UK vehicle by registration plate. Answers what car a registration belongs to, whether it is taxed and when tax is due, whether its MOT is valid and when it runs out, and whether a safety recall is outstanding. Returns the make, model, colour, fuel type and year, the MOT status and expiry date, the tax status and due date, and the recall status, with a link that opens the full free result for that registration on MotifyMe (MOT history and a free valuation). Does not include outstanding finance, insurance write-offs or stolen records, which are only in the paid vehicle history check. Rate limited.

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": {
      "registration": "<registration>"
    },
    "name": "free_vehicle_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
registrationYesUK registration plate, for example AB12 CDE

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 readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered; the description adds real value on top by disclosing the exact data returned, the included external link to the MotifyMe result page, and the scope exclusions. The rate-limit disclosure is only the bare phrase 'Rate limited' with no threshold, window, or failure behaviour, which is the one substantive gap.

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?

Front-loaded with the core purpose in the first sentence, then progressively adds coverage, return fields, exclusions, and limitations. It is dense rather than bloated, though the enumerated return-field list is long and could be tightened; 'Rate limited.' as a terminal fragment is terse to the point of being uninformative.

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?

With no output schema and only one trivial parameter, the description carries the full burden of describing results, and it does so concretely: make, model, colour, fuel type, year, MOT status and expiry, tax status and due date, recall status, plus a result link. Exclusions and a rate-limit caveat round out what an agent needs to call it and set expectations.

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?

There is a single required parameter at 100% schema description coverage, and the schema already supplies the meaning plus the 'AB12 CDE' format example. The description's 'by registration plate' merely restates the schema and adds no new syntax, normalization, or validation guidance, 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?

States a specific verb and resource ('Free check of a UK vehicle by registration plate') and then enumerates the exact questions answered: registered keeper vehicle identity, tax status/due date, MOT validity/expiry, and outstanding recalls. It also draws the boundary against the paid vehicle history check, so an agent can distinguish it from vehicle_history_check without further inspection.

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?

Explicitly states what the tool does NOT cover ('outstanding finance, insurance write-offs or stolen records') and where that data lives ('only in the paid vehicle history check'), which routes the agent to the right alternative for those needs. What's missing is an explicit trigger condition such as 'use this first when you only need tax/MOT/recall status' or a note on when the free link result is insufficient.

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