Skip to main content
Glama

Mechanic Atlas Auto Manual

NHTSA Recalls

recalls
Read-onlyIdempotent

Safety recalls for a year, make and model from NHTSA, read live.

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": {
      "year": "<year>",
      "make": "<make>",
      "model": "<model>"
    },
    "name": "recalls"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeYesMake, for example Toyota
yearYesModel year, for example 2015
modelYesModel, for example Camry

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and external-dependency profile is covered structurally. The phrase 'read live' adds a small amount of context — that results are fetched live from NHTSA rather than cached — but nothing about empty results, result granularity, or failure modes is disclosed.

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?

A single short sentence with the resource and its scope front-loaded and no filler. Every element — safety recalls, year/make/model, NHTSA, live — carries information.

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 simple three-required-parameter read tool with full schema coverage and rich annotations, most of what an agent needs is present. The gap is on the output side: with no output schema, the description should hint at what a recall record contains (campaign number, component, remedy) and what an empty response means.

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%, with each of year, make and model documented and exemplified in the schema itself, so the schema does the heavy lifting. The description restates the same three inputs without adding format rules (e.g., case sensitivity, make naming conventions, model-year ranges).

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 resource (safety recalls), its authoritative source (NHTSA), and the exact scope (year, make, model), which lets an agent distinguish it from sibling tools like complaints. The verb is only implied ('for ... from NHTSA'), so it is slightly less crisp than an explicit 'list/fetch', but the intent is unambiguous.

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 implied by the vehicle-scoped phrasing: call it when you need recall information for a specific year/make/model. There is no explicit statement of when not to use it and no pointer to a sibling such as complaints or find_vehicle, so the agent must infer routing from names alone.

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