open-data-mcp

dataandbeyond--vin-decoder-recalls

Read-only

Decode multiple VINs and check NHTSA safety recalls in one batch call, returning vehicle details plus recall campaigns for each make, model, and year.

Instructions

Bulk VIN decoding and NHTSA recall check. Calls NHTSA vPIC and Recalls APIs directly (U.S. public domain).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dataandbeyond--vin-decoder-recalls"
  }
}

Input Schema

Name	Required	Description
`vins`	No	17-character VINs. Example values: ["1HGCM82633A004352"]
`maxItems`	No	Max VINs Example values: 10000
`waitSecs`	No	Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
`includeRecalls`	No	Adds NHTSA recall campaigns for make/model/year. Example values: true

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Oct 30, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is clear. The description adds that it calls NHTSA APIs directly and that the data is U.S. public domain, which is useful context, but it does not disclose rate limits, error handling, or return behavior beyond what the schema's waitSecs parameter already explains.

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, front-loaded with the core purpose, and no waste. Every word contributes to understanding what the tool does and its data source.

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?

There is no output schema, and the description does not explain what the tool returns (e.g., decoded vehicle attributes and recall campaigns). For a data-returning tool, this leaves a gap in completeness, though the parameter schema covers operational details like waitSecs and maxItems.

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%, so all four parameters are fully documented in the schema. The description does not add any parameter-specific meaning beyond what the schema provides, which is the baseline expectation when schema coverage is high.

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?

The description states a specific verb and resource: 'Bulk VIN decoding and NHTSA recall check.' It distinguishes the tool's dual function from unrelated siblings and leaves no ambiguity about what it does.

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?

The word 'Bulk' implies the tool is for multiple VINs, but there is no explicit guidance on when to use it versus alternatives, nor any exclusions or prerequisites. Usage is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server