Skip to main content
Glama

CarMax used cars for a make: stock number, VIN, year, make

auto_carmax
Read-only

CarMax used cars for a make (and optional model): stock number, VIN, year, make, model, trim, body, price, original price and price-drop flag, mileage, colors, drivetrain, engine, MPG, store name/city/state, highlights (single owner, warranty...), date listed and link; about 20-24 per page, plus the nationwide total. From carmax.com's public search pages via a residential proxy. Related tools on this server, for a different need: auto_carvana when you need Carvana used cars for a make: year, make, model, trim; auto_autonation when you need AutoNation cars for sale for a make and optional model. Price: $0.002 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_carmax"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeYesCar make, e.g. toyota, ford, tesla
modelNoOptional model, e.g. camry, f-150, 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, so the safety profile is covered; the description goes further by disclosing page size (~20-24 per page) with a nationwide total, the data source (public carmax.com search pages via residential proxy), and the billing model ($0.002 per successful call, x402/USDC, failures not charged). The only gap is that it doesn't say how the nationwide total relates to the per-page listing (i.e., whether pagination parameters exist), but it adds substantial context 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.

Conciseness4/5

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

Purpose and scope are front-loaded, and every clause — field inventory, page size, source, cost — contributes information an agent would otherwise have to discover. It loses a point for being a single dense run-on with semicolon-separated lists that make the routing guidance harder to scan.

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?

An output schema exists, so return values need not be spelled out, yet the description still summarizes the field set, page size, source, and per-call cost. For a two-parameter read-only search tool, nothing needed to call it correctly is missing.

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 both parameters carry examples (toyota, camry), so the schema already does the heavy lifting for make/model semantics. The description restates the same 'make and optional model' framing and adds matching examples only implicitly via the returned field list, so it doesn't meaningfully extend the parameters beyond the structured data.

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?

The description opens with a specific verb+resource pairing, 'CarMax used cars for a make (and optional model)', then enumerates the exact fields returned. It also explicitly names the sibling alternatives (auto_carvana, auto_autonation) and the source domain, so an agent can distinguish it from every other auto tool 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?

It states the selection condition directly: use this for CarMax inventory, use auto_carvana for Carvana and auto_autonation for AutoNation, each with its own field coverage. That is explicit when-to-use and when-to-use-something-else guidance rather than an implied hint.

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