Skip to main content
Glama

Vin decode

vin_decode
Read-onlyIdempotent

Decode any 17-character ISO 3779 Vehicle Identification Number (VIN): local checksum + WMI validation and official US DOT NHTSA vPIC make, model, year, body, engine, fuel and plant data. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYes17-character VIN (excluding I, O, and Q)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

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?

Annotations only declare readOnly/idempotent/non-destructive/openWorld; the description adds the details that actually matter here — a $0.002 per-call charge, accepted rails (USDC on Arc, Base or Solana; XNT on X1), and the requirement that a payment handshake complete inside a second invocation. Cost and auth flow are exactly the operational facts annotations cannot express.

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?

Two sentences, front-loaded with the capability, then pricing, rails and the call-twice protocol. Dense with payment jargon but every clause carries operational information an agent needs before invoking.

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?

No output schema exists, and the description compensates by naming the returned fields (make, model, year, body, engine, fuel, plant) plus the validation results. Input constraints, cost, and settlement flow are all covered, so nothing essential is missing for a two-parameter paid lookup tool.

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

Parameters4/5

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

Schema coverage is 100%, so the parameters are already documented and the baseline is 3. The description goes beyond the schema by explaining the sequencing of the `payment` parameter — first call returns terms, second call with the signed payload settles the purchase — which the schema alone does not convey.

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 — decoding a 17-character ISO 3779 VIN — and enumerates the exact work performed: local checksum, WMI validation, and official NHTSA vPIC lookups for make, model, year, body, engine, fuel and plant. That is enough to separate it from generic decoders like calldata_decode or evm_log_decode without opening either schema.

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?

Gives concrete procedural guidance for the two-step purchase: call once without `payment` to get terms, sign with your own wallet, call again with `payment`. There is no explicit when-not-to-use or named alternative, but the scope is narrow enough that an agent knows the domain it applies to.

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