Skip to main content
Glama

Tesla VIN Report

Used Tesla buyer's guide

used_tesla_buyer_guide
Read-onlyIdempotent

What to check before buying a used Tesla of one model and model year, for example a 2016 Model S. Returns the short answer, the main checks with one line each, the free-Supercharging rule for those cars, the Autopilot and media computers they were built with, and the page to read. For the years the paid Service Report is sold for, it says what that report adds, with a sample. It does not look up any car: check_tesla_vin answers for one car, by its VIN.

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": {
      "model": "<model>",
      "year": "<year>"
    },
    "name": "used_tesla_buyer_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesThe model year, for example 2016.
modelYesThe model line.

Output Schema

NameRequiredDescriptionDefault
okYes
urlNo
yearNo
errorNo
limitNo
modelNo
titleNo
checksNo
messageNo
relatedNo
computersNo
short_answerNo
retry_after_sNo
service_reportNo
years_availableNo
free_superchargingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered; the description adds the substantive behavior of the response: which checks, the free-Supercharging rule, the hardware fitted, and that paid Service Report coverage is signalled with a sample. It omits anything about freshness/caching of the guide data or rate limits, which keeps it short of a 5 for a tool whose value hinges on data currency.

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?

Front-loaded with the purpose, then the payload, then the sibling exclusion — a sensible order with no filler. It is somewhat dense and spends a long clause enumerating return contents that the output schema already covers, which is the only thing keeping it from a 5.

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?

With annotations covering safety, 100% schema coverage, and an output schema defining the return shape, the description supplies exactly the missing layer: which model/year granularity is supported, what the answer contains, and how it differs from the VIN tool. An agent has everything needed to call it correctly and interpret the reply.

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 model enum plus year range are fully documented in the schema, so the baseline is 3. The description's 'for example a 2016 Model S' usefully shows the two parameters working together as a pair, but adds no format, edge-case, or granularity guidance beyond that.

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 resource and scope: a buyer's guide for one Tesla model line and model year, and enumerates what comes back (short answer, main checks, Supercharging rule, Autopilot and media computers, page link). It explicitly distinguishes itself from the VIN lookup sibling, so an agent can choose between them 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 Guidelines5/5

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

The opening clause ('What to check before buying a used Tesla of one model and model year, for example a 2016 Model S') gives the use case directly, and the closing sentence supplies the exclusion plus the alternative: 'It does not look up any car: check_tesla_vin answers for one car, by its VIN.' Both when-to-use and when-not-to-use are explicit.

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