Skip to main content
Glama

Vehicle history check: stolen, written off or on finance

vehicle_history_check
Read-onlyIdempotent

What the paid MotifyMe vehicle history check covers and the link to run it: stolen markers, insurance write-offs (Cat S, Cat N and older categories), outstanding finance, scrapped or salvaged, imported or exported, plate and colour changes, and number of previous keepers, for buyers and sellers of UK cars. This tool does not look up those records and its result is not confirmation that a vehicle is clear. The link has the registration filled in when one is 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": "vehicle_history_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
registrationNoOptional UK registration plate, for example AB12 CDE

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 already declare a safe, idempotent, closed-world read, and the description adds the disclosure that matters most: this tool does not look up the records at all and its result is not confirmation that a vehicle is clear. It also explains that the deliverable is a link with the registration prefilled, which prevents an agent from treating a returned value as a pass/fail verdict.

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 front-loads what the check covers and the link, but the critical limitation sentence sits after a long comma-separated enumeration, so the most decision-relevant caveat is not leading. The category list is long yet each item maps to a real user intent worth matching against.

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?

There is no output schema, and the description compensates by explaining what is returned (a link, registration prefilled) and, importantly, what is not returned (the actual records, no clearance confirmation). Nothing an agent needs in order to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description goes beyond the schema by explaining the effect of supplying the parameter: the returned link has the registration filled in when one is given. That clarifies that the parameter is optional and pre-populates rather than filters or validates.

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 names a specific resource (a paid MotifyMe vehicle history check) and enumerates exactly which record categories it covers — stolen, write-offs with category names, finance, salvage, imports/exports, plate/colour changes, keeper count. The 'paid' qualifier implicitly separates it from a free-check sibling without naming one, so the sibling differentiation is only partial.

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

Usage Guidelines3/5

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

It gives an audience context ('for buyers and sellers of UK cars'), which implies when the tool is relevant, but never states when to prefer it over a free check or when it is unnecessary. There is no explicit routing to or away from any alternative.

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