L50 UK Data API

mot history

mot_history

Read-only

UK MOT history for one vehicle from official DVSA data: make, model and age, MOT valid and expiry date, every test result, mileage history with a clocking warning (mileage that went down), last test's advisories and dangerous defects, and repeat failures. No owner data. Costs $0.02 per call, paid in USDC on Base with x402.

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": "mot_history"
  }
}

Input Schema

Name	Required	Description	Default
`full`	No	Include defects and mileage history (default true)
`registration`	Yes	UK number plate, with or without spaces, e.g. AB12 CDE

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already mark it read-only and open-world, and the description adds genuinely new behavior: a $0.02 per-call charge paid in USDC on Base via x402, plus the fact that a clocking warning is derived from mileage decreases and that owner data is excluded. It does not cover failure behavior for an unknown registration, but the commercial terms are a valuable disclosure.

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, then a dense but purposeful contents list, closing with cost and a data-scope exclusion. The enumeration is long but every item is a distinct return field, so little could be cut.

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 heavy lifting by enumerating returned fields, and it adds pricing and data-exclusion context. Only edge cases (invalid/unknown plate behavior, coverage period) are unaddressed.

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 both parameters are already documented, and the description's contents list maps loosely to the 'full' flag without explicitly sayings what that flag toggles. 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?

Names a specific verb+resource (UK MOT history for one vehicle) and enumerates the returned data precisely (make/model/age, expiry, test results, mileage, advisories/defects, repeat failures). No sibling tool covers MOT data, so the agent can route to it unambiguously.

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?

'For one vehicle' implies one lookup per registration and 'No owner data' sets expectations about scope, but there is no explicit when-to-use/when-not-to-use guidance or mention of alternatives. Usage is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All L50 UK Data API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?