Skip to main content
Glama

US NHTSA safety recalls for a make, model and model year

auto_nhtsa_vehicle_recalls
Read-only

US NHTSA safety recalls for a make, model and model year: campaign number, component, summary, report date and remedy flags, as published by NHTSA. Recalls only; no VIN lookup and no recall status (open/closed). Related tools on this server, for a different need: auto_nhtsa_vehicle_complaints when you need US NHTSA owner-filed vehicle complaints for a make, model; auto_nhtsa_vpic_vehicle_decoder when you need to decode a VIN with NHTSA vPIC: make, manufacturer, model. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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>",
      "year": "<year>"
    },
    "name": "auto_nhtsa_vehicle_recalls"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeYesVehicle make, e.g. honda
yearYesModel year, 1950 to 2100
modelYesVehicle model, e.g. accord

Output Schema

NameRequiredDescriptionDefault
makeNo
yearNo
countNo
modelNo
sourceNo
recallsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only and open-world, so the safety profile is covered; the description adds materially new behavior: authoritative source (as published by NHTSA), coverage exclusions, and a per-call price with payment rail (x402, USDC) where failed calls are not charged. The only omission is anything about result volume or pagination, which keeps it from a 5.

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?

Front-loaded with purpose and return fields, then boundaries, then sibling routing, then cost — a sensible priority order with no filler. It is dense and slightly crammed (the 'Recalls only' fragment and the long payment sentence), but every sentence carries usable information.

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 three required, fully documented parameters and an output schema, the description covers what to expect, what is excluded, and the cost of invocation. Only result-size or pagination expectations are unaddressed, a minor gap given the output schema.

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%, including the 1950–2100 year range and make/model examples, so the schema carries parameter meaning entirely. The description only restates the make/model/year triple and adds no format or normalization hints beyond it — baseline 3 applies.

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+resource (US NHTSA safety recalls) scoped to make/model/year, then enumerates returned fields (campaign number, component, summary, report date, remedy flags). It explicitly draws boundaries — 'Recalls only; no VIN lookup and no recall status' — so an agent can separate it from the decoder and complaint tools 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?

Names concrete alternatives with the condition that selects each: complaints tool 'when you need US NHTSA owner-filed vehicle complaints', decoder 'when you need to decode a VIN'. Negative guidance is also explicit (no VIN lookup, no open/closed status), leaving no inference required.

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