Skip to main content
Glama

GetFreeCarCheck: UK car reliability and MOT data

Free car check by registration

check_vehicle
Read-only

Free UK car check by number plate: MOT history, mileage record with rollback warnings, ULEZ, road tax, recalls and reliability. Needs a free GetFreeCarCheck API key (getfreecarcheck.co.uk/developers).

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

Input Schema

NameRequiredDescriptionDefault
registrationYes

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 declare readOnlyHint and openWorldHint, so the safety profile is covered by structured data. The description adds genuinely useful context beyond that: it names the prerequisite free API key and where to obtain it, which is exactly the kind of setup/auth information an agent cannot get from the schema or annotations. It stops short of noting rate limits, key-failure behavior, or response shape.

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?

Two dense sentences, front-loaded with the core capability and followed by the prerequisite. Every clause carries information; the only slight redundancy is the repeated 'Free', used once as a product attribute and once as an API-key qualifier.

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?

There is no output schema, so the description must signal what comes back — it does so by listing the six check categories. For a single-parameter read-only lookup, that covers nearly everything an agent needs; the missing piece is any hint about result format or whether categories can be absent for a given plate.

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?

With one parameter at 0% schema description coverage, the description carries the burden and does partially compensate: 'by number plate' and 'UK' clarify that 'registration' means a UK license plate, not an ID or account number. It does not specify format expectations (spaces, casing, validity errors), so the semantic value added is real but thin.

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 specific verb and resource ('UK car check by number plate') and enumerates the data domains covered (MOT history, mileage, ULEZ, road tax, recalls, reliability), so an agent knows exactly what it gets back. It does not, however, distinguish itself from siblings like mileage_check, ulez_check, or road_tax, which cover overlapping ground — the reader must infer this is the aggregate/all-in-one option.

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 implied rather than stated: an agent can infer it should call this with a UK registration for a broad snapshot. There is no explicit guidance on when to prefer this over the narrower sibling tools (e.g. 'use this for an overview; use mileage_check for detailed mileage'), and no exclusions or edge cases.

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.