Skip to main content
Glama

MOT Index fleet statistics

mot_index
Read-onlyIdempotent

MOT statistics for the whole GB fleet, from the RegTail MOT Index 2025 (DVSA anonymised MOT data, Open Government Licence v3.0). Answers: how often a model passes its MOT, what fails and what gets advisories, how it compares with all cars, by age, fuel and mileage, and how a model at a given age compares with all cars of that age (pass age). Free, no account or credit needed, read-only. Beta: the figures are final for this release, field names may still change.

Aggregate figures, not a check of any particular car: for one car use the plate tools. Pass node as a stable id: overview, index (every node id), postcode, release, model/{make}/{model} (e.g. model/ford/fiesta), make/{make}, defect/{slug}; a page URL or a name like 'Ford Fiesta' also works. year is 2023, 2024, 2025 or latest. view='full' adds the long lists.

Returns summary (one sentence), data (rates are fractions 0 to 1; failure and advisory rates are floors, say 'at least'; fuel, mileage-band and postcode figures are not age-adjusted), evidence (sources, as-of, population, uncertainty, insufficient_data with its reason when a year has too few tests: then say there are not enough tests, never give a number), links, edges (the next nodes, what each answers, free, thin) and citation. Cite it as DVSA anonymised MOT data. It does not check outstanding finance, stolen or write-off status.

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

Input Schema

NameRequiredDescriptionDefault
ageNoModel or overview nodes: compare cars of this age in years
nodeNoNode id (model/ford/fiesta, make/ford, defect/oil-leak, overview, index, postcode, release), a /mot page URL, or a name like 'Ford Fiesta'overview
viewNosummary (small) or full (adds the long lists)summary
yearNo2023, 2024, 2025 or latest (default: the node's newest year with figures)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is largely covered. The description does add genuinely non-obvious behavioral caveats: failure/advisory rates are floors ('say at least'), fuel/mileage/postcode figures are not age-adjusted, and insufficient_data must be reported as 'not enough tests' with no number. It also scopes out finance/stolen/write-off checks, so this is above the annotation baseline.

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 purpose in the first sentence, then usage, then return shape and limitations. Dense semicolon-separated clauses (node list, returning fields) pack a lot into little space, but the compression makes it slightly harder to parse than a plain bulleted structure would be.

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?

Despite an output schema existing, the description pre-empts the traps an agent would otherwise fall into: fractional rates, floor semantics, non-age-adjusted segments, insufficient-data handling, citation requirement, and explicit exclusions. For a data-lookup tool with four optional params, nothing material is left unstated.

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 all four parameters are already documented with enums and defaults. The description restates the node forms and year values rather than adding new syntax, and its only genuine semantic addition is the framing of age comparisons ('pass age') and what view='full' unlocks. 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 resource and data source (whole-GB-fleet MOT statistics from the RegTail MOT Index 2025) with a concrete question set it answers (pass rates, failures, advisories, age/fuel/mileage comparisons). It explicitly distinguishes itself from the plate tools, so an agent can separate it from decode_plate/full_report without opening any schema.

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

Usage Guidelines5/5

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

Names the alternative route ('for one car use the plate tools'), enumerates the acceptable node forms including a discovery node ('index (every node id)'), and spells out year values and the view trade-off. Cost/access guidance ('free, no account or credit needed') is also given, which removes the usual prerequisite uncertainty.

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