Skip to main content
Glama

decode_vin

Read-only

Decode a VIN and return a vehicle report: specs, recalls (with manufacturer build-date ranges), a complaint summary with the most recent complaints, safety ratings, fuel economy, EPA test-vehicle data, parts content and origin (MY2020+), historical production and theft (MY1998-2012), and photo URLs. decode_checks checks the official decode field by field (drive, engine, electrification, transmission, speeds, seats, GVWR) against the manufacturer's description of this VIN, NHTSA test vehicles with the same VIN pattern and EPA's configurations: confirmed, corrected, doubtful or filled, with vPIC's original value kept.

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

NameRequiredDescriptionDefault
vinYes17-character Vehicle Identification Number
transmissionNoTransmission, when the owner knows it and the VIN does not say. Applies to fuel economy only when EPA lists the model with both; without it an automatic is assumed and marked (fuel_economy.assumed, alternatives).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / transmission
      Added value: +{
      +  "description": "Transmission, when the owner knows it and the VIN does not say. Applies to fuel economy only when EPA lists the model with both; without it an automatic is assumed and marked (fuel_economy.assumed, alternatives).",
      +  "enum": [
      +    "automatic",
      +    "manual"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, openWorldHint true, destructiveHint false), so the description's real value is disclosing the breadth and conditional nature of the output, e.g. parts content only for MY2020+ and theft/production only for MY1998-2012. It does not mention rate limits or auth, but the year-gated coverage and assumed-transmission behavior are meaningful beyond the 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?

Two sentences, purpose front-loaded, and every clause names concrete report sections rather than filler. The second sentence is a dense run-on enumerating many fields, which costs a little readability but earns its space.

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?

There is no output schema, so the description carries the return-value burden — and it does so by enumerating the report sections and even describing the decode_checks confirmation/correction semantics. For a read-only lookup with only one required parameter, an agent has enough to call it and interpret what comes back.

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%, and the schema's own transmission description already explains the fuel-economy fallback (automatic assumed and marked). The description adds no further parameter meaning, so the baseline 3 applies even though both parameters are well documented elsewhere.

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?

Opens with a specific verb+resource ("Decode a VIN") and then enumerates exactly what the report contains, from specs and recalls to theft history and photo URLs. That is far more concrete than a tautology, but it never names a sibling (validate_vin, batch_decode, lookup_recalls) to anchor what this tool is not.

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 is implied rather than stated: an agent can infer this is the full vehicle-report call, but there is no explicit when-to-use guidance, no exclusions, and no pointer to an alternative for validation-only or batch cases. The one conditional rule given is about the transmission parameter, not about tool selection.

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.