Skip to main content
Glama

Get one listing by VIN

get_listing
Read-onlyIdempotent

One listing by VIN: every field of the search record plus its asking-price history on this seller, and battery_warranty, this car's high-voltage battery warranty as its Census EV page gives it: status (for example "Expired" or "In force · 38,200 mi or 3+ yr left"), in_force, and estimated when the term is not the manufacturer's own figure. battery_warranty is absent where the page gives no verdict for the car. asking_vs_similar ("below", "typical" or "above") compares the asking price with similar cars on Census EV: the same version and model year within 40,000 miles, adjusted for mileage, counting cars listed now and cars no longer listed in the last 30 days at their last asking price. It compares asking prices and is not an appraisal. "below" and "above" need a gap of at least $1,000 that is also wider than the usual spread of asking prices for that version: for most cars about 3 to 7% over for "above" and about 5 to 9% under for "below", more where few similar cars are known, and "below" must still hold with any one similar car left out. Otherwise it is "typical". Absent when the car could not be compared: new or under 2,000 miles, no asking price or mileage, a disclosed buyback or branded title, fewer than 3 similar cars, similar cars that are not all one version, or an asking price so far under them that the gap is more than 30% of it. The seller link forwards through censusev.com to the dealer's own page for the car.

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

Input Schema

NameRequiredDescriptionDefault
vinYes17-character VIN.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower; the description still adds substantial context, including the exact absence conditions for battery_warranty and asking_vs_similar and the fact that asking_vs_similar is a price comparison rather than an appraisal. It does not describe error/not-found behavior, but the field-level semantics go well 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.

Conciseness2/5

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

The return-shape and comparison-methodology detail is accurate but heavily over-specified for a definition: exact percentage bands (3 to 7%, 5 to 9%), the $1,000 threshold, the leave-one-out rule, and the 30% exclusion occupy most of the text. The lead sentence is well front-loaded, but a long block of statistical caveats dilutes the actionable signal an agent needs.

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, so the description must carry the return contract, and it does so thoroughly: it enumerates the returned fields, explains each enum value's meaning, and states precisely when a field is omitted. For a single-parameter read tool this leaves nothing material an agent needs in order to call or interpret it.

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?

There is only one parameter, vin, and schema description coverage is 100% ('17-character VIN'), so the schema already carries the format constraint. The description adds no additional VIN semantics (no case handling, no alternate identifiers, no normalization rules), so 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?

Opens with a specific verb+resource+key: 'One listing by VIN' followed by exactly what is returned (every search-record field, asking-price history, battery_warranty, asking_vs_similar). This is clearly distinguishable from search_listings (multi-result search) and compare_listings, so an agent can route without opening the schema.

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?

The by-VIN scope implies this is the single-record lookup versus search_listings, and the note that the seller link forwards through censeo.com to the dealer page tells the agent what happens on click. But there is no explicit statement of when to prefer this over a search or comparison, and no guidance on what to do when a VIN is not found.

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