Skip to main content
Glama

Standard Issue Data

Look up a VIN

lookup_vin
Read-onlyIdempotent

Return VIN-pattern identity, model-level NHTSA recalls and complaints, configuration-level NHTSA crash ratings, EPA configurations, and exact-VIN listings, dated asking-price changes, and timestamped auction bids. A reviewed factory sticker total and seller-stated MSRP appear in separate fields when available. The public playground includes a saved confirmed-sale example for VIN WBSCD9321WEE08212. An account key includes closed-auction bids and source-confirmed sales for other covered VINs. Source status explains missing or unavailable data.

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": "lookup_vin"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYesThe vehicle’s 17-character VIN.

Output Schema

NameRequiredDescriptionDefault
vinYes
recallsYes
versionYes
identityYes
complaintsYes
bid_historyYes
fuel_economyYes
retrieved_atYes
price_historyYes
safety_ratingsNoNHTSA ratings for tested configurations. Present on live lookups.
history_reportsYes
listing_historyYes
transaction_historyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and open-world behavior, and the description adds genuinely useful context beyond them: data can be missing and 'source status' explains why, and an account key changes what is returned (closed-auction bids, source-confirmed sales). It also points to a concrete confirmed-sale example for verification. It stops short of describing pagination, latency, or any rate/cost limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two long sentences are dense but the opening is a wall of output-field enumeration that duplicates the existing output schema rather than leading with what the tool does. The account-tier and source-status sentences are the most valuable and are buried at the end. Trimming the return-field list would sharpen it considerably.

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

Completeness3/5

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

An output schema exists, so most of the description's return-value detail is redundant, while the genuinely useful completeness items (auth tier effects, missing-data signaling) are present but brief. For a single-parameter read tool with annotations and an output schema, this is adequate but spends its budget in the wrong place.

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 single 'vin' parameter is fully documented with pattern and max length, so the baseline of 3 applies. The description adds no syntax or format guidance beyond the schema, only an example VIN value, which is marginal added meaning.

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?

The verb 'Return' plus the enumeration of VIN-derived data (identity, recalls, crash ratings, EPA configurations, listings, bids) makes clear this is a VIN-keyed data retrieval tool. The resource is unambiguous and the scope (model-level vs configuration-level vs exact-VIN) is unusually precise. It loses a point for framing the purpose almost entirely as an output list rather than stating 'look up vehicle data for a given VIN' up front.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to use this tool, no prerequisites, and no alternatives to consider. The only quasi-guidance is that an account key unlocks additional data, which is a capability note rather than a usage rule. An agent must infer all invocation context.

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