Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

carmax_search_suggestions

Retrieve CarMax autocomplete suggestions for partial make, model, or trim searches, with typo-tolerant matching by default and optional exact-prefix mode.

Instructions

Get CarMax search autocomplete suggestions. Returns autocomplete suggestions for a partial search term (make/model/trim), typo-tolerant by default.

Input Schema

NameRequiredDescriptionDefault
searchYesFree-text partial search term to get autocomplete suggestions for
exact_matchNoDisable fuzzy/typo-tolerant matching -- require an exact prefix match. Defaults to false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description must carry the behavioral burden. It discloses that matching is typo-tolerant by default, which is useful, but it does not describe result limits, response shape, or other operational behavior beyond what is already in the schema.

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?

The description is two tight sentences with no wasted text. The core purpose is front-loaded, and the typo-tolerance behavior follows immediately.

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?

For a simple two-parameter autocomplete tool with full schema coverage and no output schema, the description is nearly complete. It states the return type and the key matching behavior, though a brief note on expected result form would make it fully self-contained.

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 both parameters thoroughly. The description adds a make/model/trim example and repeats the typo-tolerant default, but does not add substantial meaning beyond the structured parameter descriptions.

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?

The description gives a specific verb and resource: 'Get CarMax search autocomplete suggestions.' It also clarifies that it returns suggestions for partial make/model/trim terms, which distinguishes it from a full search tool, though it does not explicitly name the sibling search tool.

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 implies usage for partial search terms and names the domain as make/model/trim, but it does not explicitly state when to use this instead of carmax_search or how to handle the transition from suggestions to actual results.

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