Skip to main content
Glama

GetFreeCarCheck: UK car reliability and MOT data

Fetch a car model's reliability report

fetch
Read-only

Fetch the full reliability report for a model id from search.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the report returned is "full" (as opposed to a summary), which is real behavioral context, but it says nothing about failure modes for an unknown id or what the response contains, and no output schema exists to fill that gap.

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?

One sentence, front-loaded with the verb and result, with no filler. The only weakness is that the closing phrase "from search" is terse enough to be slightly ambiguous about whether it names a source tool or a search scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with annotations covering safety, the description is close to sufficient, but with no output schema it should say more about what the "full reliability report" returns or what happens on an invalid id. It is adequate rather than complete.

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 0% for the single required "id" parameter, so the description must carry the burden. It does add provenance ("model id from search"), which is the most important thing to know, but it does not clarify the id's format or whether it identifies a model versus a specific variant/trim.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Fetch the full reliability report for a model id" gives a verb and a resource, so the action is guessable, but the tool name "fetch" is generic and the description never distinguishes this from the sibling "car_reliability", which plausibly returns the same data. An agent cannot confidently choose between them from this text alone.

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?

"from search" implies a workflow prerequisite: the id must first come from the search tool, which is genuinely useful routing information. However, there is no statement of when to prefer this over car_reliability, compare_cars, or most_reliable_cars, and no exclusion or precondition beyond that implied chaining.

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.