Skip to main content
Glama

Tesla VIN Report

Check a Tesla VIN

check_tesla_vin
Read-onlyIdempotent

Check a used Tesla by its VIN. Use it when someone gives you a 17-character Tesla VIN, for example from a listing. From Tesla's own record for that car it returns whether Full Self-Driving is on it, the Autopilot computer, the battery pack and the build date. It also returns the model, model year and plant from the VIN, the number of NHTSA recalls and of Tesla's service bulletins for the model year, and links for the person. On free Supercharging it gives the rule for a car that cannot have it. For a Model S or Model X built before April 2017 it says the answer is in the paid Factory Report, with that report's link. For a Model S of 2012 to 2016 or a 2016 Model X it also returns the paid Service Report, which goes through those service bulletins for the car, with its link and a sample. It does not cover battery health, accidents, title history or mileage. Read-only and free, within a daily limit.

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

Input Schema

NameRequiredDescriptionDefault
vinYesThe car's 17-character VIN, as on the listing or the label in the driver's door frame.

Output Schema

NameRequiredDescriptionDefault
okYes
carNo
urlNo
vinNo
builtNo
errorNo
limitNo
linksNo
reportNo
messageNo
recallsNo
identityNo
built_forNo
for_sellersNo
battery_packNo
not_includedNo
retry_after_sNo
service_reportNo
full_self_drivingNo
service_bulletinsNo
autopilot_computerNo
free_superchargingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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; the description adds real context beyond them: it is free but subject to a daily limit, and it discloses conditional behavior such as the paid Factory Report fallback for pre-April-2017 Model S/X and the paid Service Report for 2012-2016 Model S and 2016 Model X. Those upsell paths are exactly the kind of behavior an agent needs to anticipate.

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?

Front-loading is good — purpose and trigger come first — but the long run of sentences enumerating return fields and report upsells is dense and partly redundant with the existing output schema. It is informative rather than wasteful, yet tighter grouping would improve scanability.

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 single-parameter tool with a rich conditional output, the description covers what is returned, the free-tier limit, the paywalled report conditions, and the explicit out-of-scope topics. An agent has everything needed to call it and to set expectations with the user.

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?

Only one parameter and schema coverage is 100%, so the schema already defines the VIN field including its 17-character form. The description restates the length and the source of the VIN but adds no syntax, validation or format detail beyond the schema; baseline 3 applies.

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 ("Check a used Tesla by its VIN") and immediately scopes it to a 17-character Tesla VIN from a listing. The enumeration of what it returns (FSD status, Autopilot computer, battery pack, build date, recalls, bulletins) makes it clearly distinguishable from the option-code and buyer-guide siblings.

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 an explicit trigger ("Use it when someone gives you a 17-character Tesla VIN") and explicit exclusions ("does not cover battery health, accidents, title history or mileage"), which steers the agent away from misusing it. It does not name a sibling or alternative for the excluded topics, so it stops just short of a 5.

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