Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

carmax_search

Search CarMax used-car listings by make, model, price, year, mileage, or ZIP, returning vehicle summaries, facets, and total match counts.

Instructions

Search CarMax vehicle listings. Searches CarMax for used car listings, returning vehicle summaries (make, model, trim, year, mileage, colors, engine, fuel economy, pricing, store, images), available search facets with live counts, and the total matching count.

Input Schema

NameRequiredDescriptionDefault
zipNo5-digit US ZIP code to bias results toward CarMax's nearest store
makeNoCarMax make, e.g. honda, Toyota, BMW (case-insensitive)
pageNo1-indexed result page, defaults to 1. CarMax returns 48 results per page
sortNoSort order: bestmatch, distance-asc, price-asc, price-desc, mileage-asc, mileage-desc, year-desc, year-asc, newarrival. Defaults to bestmatch
modelNoCarMax model, e.g. civic (case-insensitive). Does not require make
max_yearNoMaximum model year
min_yearNoMinimum model year
max_priceNoMaximum price in US dollars
min_priceNoMinimum price in US dollars
max_mileageNoMaximum odometer mileage

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses return structure — vehicle summaries with named fields, facets with live counts, and a total matching count — which is genuine behavioral context. But it says nothing about read-only nature, permissions, or rate limits, leaving gaps for a tool with zero annotation coverage.

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?

Two sentences, front-loaded with purpose followed by return contents. The field enumeration is dense but informative and earns its space given the absence of an output schema. Minor redundancy in restating 'Search CarMax'.

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

Completeness3/5

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

For a 10-parameter search with no annotations and no output schema, the description adequately compensates by explaining what is returned. However it omits how facets should be used for filtering and gives no routing context relative to the many sibling search tools, leaving the definition only minimally complete.

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 the schema already documents all ten parameters (zip, make, model, page, sort, price/year/mileage ranges). The description adds no parameter-level detail beyond this; it instead enumerates return fields. Baseline 3 is appropriate.

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?

States a specific verb (search) and resource (CarMax vehicle listings) and clearly distinguishes itself from detail-oriented siblings like carmax_vehicle by noting it returns listings. However, it doesn't distinguish itself from adjacent sibling searches (autotrader_search, carsdotcom_search) or carmax_shop_by_brand, so it's clear but lacks sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no alternatives named. The agent must infer that this is the entry-point search tool versus carmax_search_suggestions or carmax_shop_by_brand. Only implied usage is present.

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

Deploy Server

Other Tools