NHTSA Vehicle Safety

decode_vin

Decode a Vehicle Identification Number (VIN) to get vehicle details.

Returns make, model, year, body class, engine info, safety features,
and other attributes encoded in the 17-character VIN.

Args:
    vin: A 17-character Vehicle Identification Number (e.g. '1HGBH41JXMN109186').

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": {
      "vin": "<vin>"
    },
    "name": "decode_vin"
  }
}

Input Schema

Name	Required	Description	Default
`vin`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 3, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden of disclosing behavior. It accurately describes the decode operation and return content, but does not mention potential error handling, validation of the VIN, or whether the operation requires any special permissions. The read-only nature is implied but not explicitly stated.

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?

The description is concise and front-loaded, with the primary purpose in the first sentence. The Args section is clearly structured and provides necessary parameter details without redundancy.

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?

Given the simple tool with a single parameter and an output schema, the description is complete: it covers purpose, parameter format, and expected output fields. No additional context seems necessary for a user to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides no description for the 'vin' parameter (0% coverage), but the description's Args section fully compensates by specifying the 17-character format and giving a concrete example. This adds meaningful guidance beyond the raw schema.

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 clearly states the tool decodes a VIN and lists the types of details returned, making its purpose specific to vehicle identification decoding. However, it does not explicitly differentiate from sibling tools, as most other tools focus on complaints, crashes, and recalls rather than VIN decoding.

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 description implies usage when a user needs vehicle details from a VIN, but it does not explicitly state when to choose this tool over alternatives or provide any exclusion criteria. No sibling tools are referenced.

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

All NHTSA Vehicle Safety tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?