Skip to main content
Glama

BRAINIAC Vehicle VIN, Safety, Fuel Economy & On-Time

Decode a VIN via vendored vPIC

vehicle-transport_vin-decode
Read-onlyIdempotent

Decode a VIN to make, model, year, body, engine and plant fields from the vendored NHTSA vPIC standalone database. No live vPIC API call. Price $0.03 USDC. POST /api/v1/vehicle-transport/vin-decode. An unpaid call returns the x402 payment terms and does not run.

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": "vehicle-transport_vin-decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYesvin, string, length 3 to 17. Required.
modelYearNomodelYear, integer, from 1980 to 2039. Optional.
includeAllNoincludeAll, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
vinNovin. String.
decodedNodecoded. Object.
snapshotNosnapshot. String.
errorTextNoerrorText. Array.
errorCodesNoerrorCodes. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description still adds meaningful context the agent cannot see in structured fields: the data comes from a vendored database rather than a live API, the call is metered at $0.03 USDC, and an unpaid call returns x402 payment terms instead of executing. That payment-gate behavior in particular is operationally important and is not derivable from annotations.

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?

Four short front-loaded sentences: purpose and data source first, then cost, endpoint, and payment gate. Every clause carries information; the raw POST path is the only element that reads as spec boilerplate rather than agent-facing guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the description covers source of truth, price, and failure mode for unpaid calls. Minor gaps remain around the behavior of the optional modelYear override and the includeAll toggle, plus error handling for an undecodable VIN.

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 vin, modelYear and includeAll are fully documented in the schema and a 3 baseline applies. The description adds no meaning about modelYear filtering or what includeAll expands, so it neither compensates for nor improves on the 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?

States a specific verb and resource ('Decode a VIN') and enumerates the returned fields (make, model, year, body, engine, plant), which lets an agent distinguish it from vin-check-digit-validate or nhtsa-recall-by-vin by output. The 'vendored standalone database' / 'no live vPIC API call' clause further separates it from any live-API variant, though it never names a sibling directly.

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 context is implied rather than stated: the agent learns the data is local/offline and costs $0.03, which implicitly argues for it over remote lookups. There is no explicit when-to-use vs when-not guidance and no reference to the sibling VIN tools, leaving the choice to inference.

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