Skip to main content
Glama

carmax_search_inventory

Search CarMax used-vehicle inventory by make, model, year range, price range, and ZIP code to get matching vehicles with stock numbers, mileage, prices, and links.

Instructions

Search CarMax inventory for used vehicles. Filter by make, model, year range, price range, and location (ZIP code). Returns a list of matching vehicles with stock numbers, prices, mileage, and links.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "carmax_search_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNoZIP code to search near (e.g., '90210')
makeNoVehicle make/brand (e.g., 'Toyota', 'Ford', 'Honda')
limitNoNumber of results to return (default: 10, max: 25)
modelNoVehicle model (e.g., 'Camry', 'F-150', 'Civic')
year_maxNoMaximum model year (e.g., 2023)
year_minNoMinimum model year (e.g., 2018)
price_maxNoMaximum price in dollars
price_minNoMinimum price in dollars
mileage_maxNoMaximum mileage

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the return payload ('stock numbers, prices, mileage, and links'), which is genuinely useful, but says nothing about read-only nature, rate limits, pagination, or what happens when filters return zero matches.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two tight sentences: the capability first, the return shape second. Nothing is repeated or wasted, and the primary purpose is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With nine optional parameters and no output schema, the description is nearly complete — it names the filter axes and summarizes the returned fields. The only small gap is not stating that calling with no filters yields a default-sized unfiltered list.

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 every parameter is already documented with examples and the default/max for limit. The description restates make/model/year/price/location but adds no format or interaction semantics beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource ('Search CarMax inventory for used vehicles') combined with the filter dimensions and a statement of what comes back. It is clearly distinguishable from carmax_get_vehicle_details and the carvana_* siblings by the 'inventory search' framing, though it never explicitly names an alternative.

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?

Usage is only implied: an agent can infer this is the entry point for browsing listings versus fetching one vehicle's details. There is no explicit when-to-use/when-not guidance, no mention that all filters are optional, and no steering toward carmax_get_vehicle_details once a stock number is found.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.