Skip to main content
Glama

WhichTrim vehicle records

check_recalls

Read-onlyIdempotent

Every NHTSA recall campaign on file for one model year, with severity, park-outside and do-not-drive advisories and the reported completion rate. IMPORTANT: recalls apply to a build range, not to a model year, so this cannot establish whether one specific vehicle is affected — only a VIN check can: send the user to the WhichTrim recall report at https://whichtrim.com/vin/?vin=, which narrows the campaigns to that VIN's engine, drive and build month.

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

Input Schema

NameRequiredDescriptionDefault
idYesVehicle id, e.g. 2021_kia_telluride.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/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), and the description adds value beyond them: it discloses the fundamental precision limitation of model-year-scoped recall data and describes the payload (advisory flags, completion rate). That limitation is the single most important behavioral fact about this tool and is stated plainly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both load-bearing: the first describes the payload, the second front-loads 'IMPORTANT' and delivers the limitation plus remedy. No filler, and the critical caveat is placed where an agent will not miss it.

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

Completeness5/5

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

No output schema exists, so the description carries the burden of describing return content, which it does (severity, park-outside and do-not-drive advisories, completion rate). Combined with the scope caveat and redirect, an agent has everything needed to call it and to route the user correctly afterward.

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% and the schema already documents the single 'id' parameter with an example (2021_kia_telluride). The description reinforces that the id resolves to a model year rather than a VIN, which is useful framing, but adds no format or parsing detail beyond the schema. Baseline 3.

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

Purpose5/5

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

States a specific verb and resource — every NHTSA recall campaign on file for one model year — plus the fields returned (severity, park-outside/do-not-drive advisories, completion rate). It also names the boundary against the VIN-based path, so an agent can separate this from decode_vin or get_vehicle without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-not-to-use rule: recalls apply to a build range, not a model year, so this cannot establish whether one specific vehicle is affected. It then names the exact alternative (WhichTrim VIN report) and supplies the URL pattern, leaving nothing to inference.

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