Skip to main content
Glama

Check VIN recalls

check_vin_recalls
Read-onlyIdempotent

Use this when the user wants a vin decoder, recall check by vin, or batch vin decoder with vehicle recalls and XLSX and CSV reports from public NHTSA data. Up to 50 VINs and 40 source requests per call; campaigns apply to the year, make and model. Do not use for VIN-specific repair status or booking repairs.

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": {
      "vins": "<vins>"
    },
    "name": "check_vin_recalls"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinsYesVIN list to decode and check, e.g. ["1HGCV1F35JA000000"]. Up to 50 entries; duplicates are checked once.

Output Schema

NameRequiredDescriptionDefault
sourceYes
summaryYes
vehiclesYes
downloadsYes
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, open-world and non-destructive behavior, so the description does not repeat those. It adds what the annotations cannot: enforced throughput limits (50 VINs, 40 source requests per call), the data source (public NHTSA data), the report formats (XLSX/CSV), and the fact that campaign matches are scoped to year/make/model rather than to an exact VIN.

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 description is two sentences that lead with the triggering use cases and follow with limits and exclusions, and every sentence carries actionable information. Some phrasing is keyword-stuffed ('vin decoder, recall check by vin, or batch vin decoder'), which slightly blunts the otherwise tight structure.

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?

The output schema covers return values, so the description does not need to explain them. The description supplies the practical limits, the data provenance, the report formats and the scope of a campaign match, which is enough for an agent to call the tool correctly. The remaining gap is not naming find_recalls_by_vehicle as the alternative for non-VIN-based lookups.

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?

The schema fully documents the single 'vins' parameter, including the 50-entry cap, the normalization of spaces/hyphens/dots, and the de-duplication of duplicates. The description's 'Up to 50 VINs' duplicates what the schema already states, and '40 source requests per call' is the only added operational detail. With 100% schema coverage, this baseline of 3 is appropriate.

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 uses specific verbs and resources: 'recall check by vin', 'vin decoder', 'batch vin decoder', with reports and NHTSA public data as the source. It hints at the boundary of the sibling tool by stating that campaigns apply to year, make and model, but it never names find_recalls_by_vehicle, so the differentiation is left partly implicit.

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

Usage Guidelines4/5

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

The description gives an explicit trigger ('Use this when the user wants a vin decoder, recall check by vin, or batch vin decoder') and explicit exclusions ('Do not use for VIN-specific repair status or booking repairs'). It does not point to the alternative sibling find_recalls_by_vehicle, so the routing guidance is incomplete rather than perfect.

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