Skip to main content
Glama

Decodes a VIN with NHTSA vPIC: make, manufacturer, model

auto_nhtsa_vpic_vehicle_decoder
Read-only

Decodes a VIN with NHTSA vPIC: make, manufacturer, model, model year, trim, vehicle type, plant city/state/country and the check-digit message. Only fields NHTSA has for that VIN are returned; no recall or history data. 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_vehicle_recalls when you need US NHTSA safety recalls for a make, model and model year. 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": {
      "vin": "<vin>"
    },
    "name": "auto_nhtsa_vpic_vehicle_decoder"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYes17-character VIN (letters I, O, Q not allowed)

Output Schema

NameRequiredDescriptionDefault
vinNo
makeNo
trimNo
modelNo
sourceNo
checkedAtNo
modelYearNo
plantCityNo
plantStateNo
vehicleTypeNo
manufacturerNo
plantCountryNo
checkDigitMessageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing partial returns ('Only fields NHTSA has for that VIN are returned'), scope exclusions ('no recall or history data'), and the payment model ($0.002 per successful call via x402 USDC, failed calls not charged). Cost and auth requirements are exactly the kind of behavioral context annotations cannot convey.

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?

Front-loads the core capability and returned fields, then sibling routing, then pricing. Every sentence serves a distinct function (scope, alternatives, cost) with no redundant restatement of the tool name or schema.

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?

For a one-input lookup with an output schema, the description supplies everything needed: what is decoded, what is deliberately absent, which sibling to use instead, and the billing consequence of a failed call. Nothing an agent needs before invoking it is missing.

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?

Only one parameter and schema coverage is 100% ('17-character VIN (letters I, O, Q not allowed)'), so the schema already carries the input contract. The description adds no syntax, format, or validation detail beyond what the schema states, which is the baseline for fully documented single-parameter tools.

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 and resource ('Decodes a VIN with NHTSA vPIC') and enumerates the exact decoded fields (make, model, model year, trim, vehicle type, plant location, check-digit message). An agent can distinguish this from the complaints and recalls siblings without opening any 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?

Explicitly routes the agent to alternatives with their conditions: 'auto_nhtsa_vehicle_complaints when you need US NHTSA owner-filed vehicle complaints for a make, model' and 'auto_nhtsa_vehicle_recalls when you need ... recalls for a make, model and model year.' The differentiator (VIN decode vs. make/model lookups) is unambiguous.

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