Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

carmax_vehicle_recommendations

Find CarMax similar-vehicle recommendations for a listing using its stock number and store ID, returning comparable vehicles with price, mileage, location, and image.

Instructions

Get CarMax "similar vehicles" recommendations for a listing. Returns CarMax's own similar-vehicle recommendations for a listing: stock number, description, display mileage/price, store location, and image, for vehicles CarMax considers comparable. An empty list is a normal result, not an error.

Input Schema

NameRequiredDescriptionDefault
store_idYesCarMax store id used as the recommendation's location context. See any search/vehicle/store response's store id field
stock_numberYesCarMax stock number to find similar vehicles for, the numeric path segment of a /car/{stock_number} URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it adds genuine value: it discloses the returned fields (stock number, description, mileage/price, store location, image) and, crucially, that 'an empty list is a normal result, not an error' — preempting an agent misreading an empty response as failure. It does not cover auth, pagination, or how 'comparable' is determined.

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 core verb+resource, and the return-field enumeration earns its place. The opening clause of sentence two ('Returns CarMax's own similar-vehicle recommendations for a listing') largely restates sentence one, a minor redundancy.

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?

No output schema exists, so the description appropriately names the fields returned and the empty-result semantic. For a simple two-required-param read tool this is nearly complete, though it omits read-only framing and any result-size/pagination expectations.

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 both stock_number and store_id are already well documented in the schema, including how to obtain them. The description adds no syntax or format meaning beyond what the schema provides, so the 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?

States a specific verb+resource ('Get CarMax "similar vehicles" recommendations for a listing') and clarifies scope via 'for vehicles CarMax considers comparable.' An agent can distinguish it from the sibling carmax_vehicle (a listing detail), but the description never names a sibling explicitly, so differentiation is implicit rather than stated.

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 phrase 'for a listing' implies this is called after identifying a listing via stock number, and the empty-list note gives mild operational guidance. However, there is no explicit when-to-use versus carmax_vehicle or carmax_search, and no stated preconditions beyond the required params.

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