Skip to main content
Glama

Carvana used cars for a make: year, make, model, trim

auto_carvana
Read-only

Carvana used cars for a make (and optional model): year, make, model, trim (from the listing text), color, mileage, price (USD), VIN, Carvana stock id, image and link, about 20 per page (page 1 to 20). From carvana.com's public inventory pages via a residential proxy. Related tools on this server, for a different need: auto_carmax when you need CarMax used cars for a make: stock number, VIN, year, make; auto_autonation when you need AutoNation cars for sale for a make and optional model. Price: $0.004 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "make": "<make>"
    },
    "name": "auto_carvana"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeYesCar make, e.g. toyota, honda, tesla
pageNoResults page 1 to 20 (default 1)
modelNoOptional model, e.g. camry, civic, model-3

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds meaningful context beyond them: the data is scraped from carvana.com public inventory pages through a residential proxy, results are capped at page 20 (~20 per page), and the call is metered at $0.004 per successful call via x402 USDC with failures not charged. That pricing and provenance disclosure is exactly the kind of behavioral detail annotations can't express; only error/empty-result behavior is left unstated.

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 resource and its returned fields, then routing, then cost — a sensible order with no filler sentences. It is dense and somewhat run-on in the field enumeration and the network/payment clause, but every element carries information 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?

With an output schema present, return values need no explanation, and annotations cover the safety profile. The description still supplies source, pagination ceiling, result density, pricing model, and sibling routing, leaving no material gap for correct invocation.

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%, so make, model, and page are already documented, giving a baseline of 3. The description adds two useful clarifications — that model is optional and that trim is parsed from listing text rather than supplied as a parameter — and confirms the ~20-per-page yield, but adds no syntax or format guidance for the parameters themselves.

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-less but unambiguous resource: Carvana used-car listings scoped by make (and optional model), and enumerates exactly what each record contains (year, make, model, trim, color, mileage, price, VIN, stock id, image, link). It also names the sibling tools (auto_carmax, auto_autonation) and the inventory source they each cover, so an agent can distinguish it from the other automotive listings tools without opening a 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?

Explicitly routes: use auto_carmax for CarMax inventory and auto_autonation for AutoNation inventory when those are the desired sources, making clear this tool is the Carvana-specific alternative. The pagination bound (page 1 to 20, ~20 per page) further frames when the tool is and isn't sufficient for a broad sweep.

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