Skip to main content
Glama

Decodes up to 20 vehicle identification numbers

vin
Read-only

Decodes up to 20 vehicle identification numbers with NHTSA's vPIC database (US public domain): make, model, model year, trim, body class, vehicle type, engine (cylinders, displacement, fuel), drive type, plant country and city, manufacturer, and the decoder's own error code and message. The check digit is verified for North American VINs. A VIN that is not 17 characters without I, O or Q is a 400. Takes about 12 s; allow a 30 s timeout. 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": "vin"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYesOne VIN, or up to 20 separated by commas (17 characters, no I, O or Q)

Output Schema

NameRequiredDescriptionDefault
countNo
sourceNo
vehiclesNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnly and openWorld, so the description carries real weight and delivers: ~12 s latency with a 30 s timeout recommendation, a documented 400 condition for malformed VINs, check-digit verification limited to North American VINs, and a pay-per-call model with failures uncharged. These are exactly the traits an agent cannot infer from structured fields.

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 and dense with actionable facts in a single block, with no filler sentences. The long enumeration of decoded fields drifts toward redundancy given an output schema exists, costing a little tightness.

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-parameter, read-only lookup backed by an output schema, the description still covers everything an agent needs to call it correctly: input validation, expected latency and timeout, cost and payment rail, and failure semantics. Nothing material is left to inference.

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 coverage is 100% and the single `vin` parameter already documents comma separation, the 20-VIN cap, and the 17-character/no-I-O-Q rule, so most of the description's parameter talk is restatement. The one genuine addition is mapping invalid input to a 400 response, which is marginally beyond the schema.

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?

Opens with a specific verb and resource ("Decodes ... vehicle identification numbers"), states the batch ceiling (up to 20), and names the underlying authority (NHTSA vPIC). The enumerated decoded fields make the scope unmistakable and no sibling competes for 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when this is the right call — decoding one to twenty VINs for specification data — and supplies the operational preconditions (30 s timeout, 17-character format). It stops short of naming exclusions or an alternative tool, but no plausible alternative exists in the supplied sibling list.

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