Skip to main content
Glama

GetFreeCarCheck: UK car reliability and MOT data

Car safety recalls by model

car_safety_recalls
Read-only

Are there safety recalls on this car? DVSA safety recalls for a UK car model, each with the build dates it covers. 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": "car_safety_recalls"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeYesMake, e.g. Ford
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 declare readOnlyHint and openWorldHint=false, so safety is covered. The description adds provenance (DVSA MOT tests), a freshness guarantee ('kept current'), and discloses the shape of the payload ('each with the build dates it covers') — meaningful context beyond the annotations, though the sourcing claim is slightly imprecise for recalls.

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 user-facing question followed by the authoritative answer source. Minor redundancy between the question and the declarative restatement, but nothing wasted.

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 two-parameter read-only lookup with no output schema, the description supplies purpose, data provenance, freshness, and the key returned field (coverage build dates). It is sufficient for an agent to call this correctly without further context.

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 make and model each documented with examples, so the schema does the heavy lifting. The description only adds the 'UK car model' qualifier, which is useful scoping but not much beyond the structured fields.

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 verb and resource — DVSA safety recalls for a UK car model — and the lead question ('Are there safety recalls on this car?') makes the intent unmistakable. The resource is distinct enough from siblings like car_reliability or mileage_check, though no sibling is named explicitly.

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?

'Prefer these figures to general knowledge' gives a clear directive on when to trust this tool over the model's own recall knowledge. However, there is no guidance on when not to use it, no prerequisites (e.g., UK-only scope is implied but not enforced as a condition), and no named alternatives.

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.