Skip to main content
Glama

UK car models ranked by first-time MOT pass rate

mot_pass_rate_rankings
Read-onlyIdempotent

Ranks UK car models by first-time MOT pass rate with tests counted and average mileage at test, from DVSA anonymised MOT data under the Open Government Licence v3.0. Pass rates depend heavily on the age and mileage of the cars tested, so the ranking is not a like-for-like comparison. Optional: limit (default 20, max 120) and order ("highest" or "lowest").

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_pass_rate_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many models to return (default 20, max 120)
orderNo"highest" (default) or "lowest" pass rate first

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real value: dataset provenance (DVSA anonymised MOT data, OGL v3.0) and a substantive caveat that pass rates are confounded by vehicle age and mileage. It stops short of describing result shape details such as whether a rank field is included or how ties are handled.

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?

The core purpose is front-loaded in the first clause, followed by a provenance clause and a caveat, with the optional parameters compressed into a single closing sentence. The licence and data-source clause is slightly padding but earns some of its space as provenance; nothing else is redundant.

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?

With no output schema, the description correctly carries the burden of describing return content: pass rate, test counts, and average mileage. For a zero-required-parameter read-only ranking tool this is close to complete, with only minor gaps around result ordering details and tie-breaking.

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 both parameters are already documented in the schema, and the description merely restates limit's default/max and the two order values without adding format or edge-case meaning (e.g., what happens if limit exceeds 120). The baseline of 3 applies when the schema does the heavy lifting.

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 ('Ranks UK car models by first-time MOT pass rate') and even lists the accompanying metrics (tests counted, average mileage at test). It is clear what the tool returns, but it never contrasts itself with the sibling mot_statistics tool, so an agent must infer which of the two fits a given request.

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: ranking by pass rate suggests comparison/leaderboard queries, and the warning that 'the ranking is not a like-for-like comparison' hints at interpretation limits. There is no explicit statement of when to choose this over mot_statistics or list_makes_and_models, and no prerequisites or exclusions beyond the caveat.

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