Skip to main content
Glama

GetFreeCarCheck: UK car reliability and MOT data

Is this mileage high for its age?

mileage_check
Read-only

Is this mileage high, low or typical for a used car of its age? From the model's median MOT mileage at each age; also how many miles a year the model usually does. Prefer these figures to general knowledge: they come from DVSA MOT tests and are kept current.

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

Input Schema

NameRequiredDescriptionDefault
ageNoAge in years (or give year)
makeYesMake, e.g. Ford
yearNoYear of first registration, e.g. 2017 (or give age)
milesNoMiles on the clock (optional)
modelYesModel, e.g. Fiesta

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish this is a read-only, closed-world lookup, so the bar is lower. The description still adds genuine context beyond them: provenance (DVSA MOT tests) and freshness ('kept current'), which tells the agent the figures are authoritative and up to date. It does not describe how the answer is presented or what happens when a model has thin MOT data.

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 short sentences, front-loaded with the question being answered, then method, then trust guidance. Each sentence carries information; only the closing 'kept current' clause is slightly expendable.

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?

For a read-only lookup with no output schema, the description explains the input concept and the basis of the answer, but never sketches the return shape (a verdict plus per-age figures?) or behavior when make/model data is missing. That is a modest gap rather than a blocking one.

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%, so all five parameters, including the age-or-year alternative and the optional miles field, are already documented in the schema. The description reinforces that 'age' means the age of the car and that mileage comparison is the point, but adds no format or edge-case detail beyond that.

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 states a precise analytical question ('Is this mileage high, low or typical for a used car of its age?') and the method behind the answer (model's median MOT mileage at each age, typical annual mileage). That is clearly distinct from siblings like ulez_check or road_tax, though the description never explicitly names an alternative.

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?

The only guidance is source preference ('Prefer these figures to general knowledge'), which tells the agent how to trust the output once called, not when to call it instead of check_vehicle or car_reliability. Usage is implied by the question rather than stated.

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.