Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

carmax_stores

Find CarMax store locations by ZIP code or keyword, returning addresses, phone numbers, opening hours, and live driving distance for nearby searches.

Instructions

Search CarMax store (physical location) locations. Searches CarMax's physical store locations by ZIP code or free-text keyword, returning stores with full address, every published phone number, opening hours, and (for a ZIP-based search) live driving distance in miles.

Input Schema

NameRequiredDescriptionDefault
zipNo5-digit US ZIP code to search near. Triggers a live geo-distance sort. Provide this or keyword; zip takes precedence if both are given
takeNoMaximum number of stores to return, defaults to 10, capped at 300
keywordNoFree-text match against store name or city

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 does well: it discloses the returned fields (full address, every published phone number, opening hours) and the conditional behavior that a ZIP search produces live driving distance in miles. It omits auth/rate-limit context, but for a read-only locator the behavioral picture is largely complete.

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?

A single front-loaded sentence covering purpose, inputs, and return contents; slightly dense with the parenthetical "(physical location)" and a run-on feel, but no wasted sentences.

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 must signal return values, which it does by listing address, phone numbers, hours, and conditional distance. Combined with the fully documented input schema, an agent has enough to call it correctly; only alternative-tool routing 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 coverage is 100%, so the schema already documents zip, take, and keyword including zip precedence. The description only restates the zip-vs-keyword duality without adding format, syntax, or precedence detail beyond the schema. 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 store (physical location) locations") and clarifies that these are physical retail locations, which meaningfully separates it from online-store tools. It does not explicitly name or contrast with the singular sibling carmax_store, so a perfect 5 is not warranted.

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 description explains the two search modes (ZIP code or free-text keyword) and implies their use, but gives no explicit guidance on when to choose this over carmax_store or other CarMax siblings. Usage is inferable rather than stated.

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