Skip to main content
Glama

MOT pass rate and common failures for a car model

mot_statistics
Read-onlyIdempotent

First-time MOT pass rate, most common failure areas and specific failures, average mileage at test and results by year of registration for a UK car model (for example make "Ford", model "Fiesta"), calculated from DVSA anonymised MOT test data under the Open Government Licence v3.0. The figures describe groups of cars, not any individual vehicle. If the model has no statistics yet, the models that do are listed.

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": {
      "make": "<make>",
      "model": "<model>"
    },
    "name": "mot_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeYesCar make, for example Ford
modelYesCar model, for example Fiesta

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 closed-world, so the safety profile is covered; the description adds genuinely new context: the DVSA anonymised MOT source under the Open Government Licence, and the important caveat that figures describe groups of cars rather than any individual vehicle. The no-statistics fallback behaviour is also disclosed. It does not discuss recency or staleness of the underlying data year.

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?

Three sentences, front-loaded with the metrics list before the provenance caveat and the empty-result fallback, each doing distinct work. The licensing sentence is the most expendable element but is short and adds trust context.

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 only two required string parameters, no output schema and full annotation coverage, the description supplies everything an agent needs: what the figures are, that they are group-level not vehicle-level, and what happens when no statistics exist. The enumerated metrics effectively stand in for the absent output schema.

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 coverage is 100%, with both make and model documented and exemplified in the schema itself, so the description's own 'make "Ford", model "Fiesta"' example adds essentially nothing new. Baseline 3 applies when the schema already carries the parameter meaning.

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 and enumerates the exact metrics returned: first-time pass rate, common failure areas and specific failures, average mileage at test, and results by registration year, scoped to a UK car model. It is unambiguous what the tool does, though it never names or contrasts itself with the sibling mot_pass_rate_rankings, so an agent must infer the boundary between a per-model lookup and a ranking.

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?

Usage is only implied through the make/model example, and the description does give one valuable behavioural cue: if the model has no statistics, the models that do are listed, which tells the agent a null-ish result is actionable rather than an error. There is no explicit statement of when to prefer this over rankings or list_makes_and_models.

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