marketplace

cars_search

Search vehicle inventory across all dealers. Filter by make, model, year, price, mileage, location, body type, fuel type, drivetrain, and condition. Returns matching vehicles with dealer info. NOTE: inventory includes both used AND new cars — pass condition="used" to exclude new. Every result states its condition.

Input Schema

TableJSON Schema

Name	Required	Description
`zip`	No	Dealer ZIP code prefix
`city`	No	Dealer city (e.g. Miami)
`make`	No	Car make (e.g. Toyota, Honda, BMW)
`limit`	No	Max results (default 20)
`model`	No	Car model (e.g. Camry, Civic, 3 Series)
`state`	No	Dealer state (e.g. FL)
`offset`	No	Pagination offset
`agent_id`	No	Your agent identifier (claude, grok, gpt, perplexity)
`year_max`	No	Maximum model year
`year_min`	No	Minimum model year
`body_type`	No	Body type (Sedan, SUV, Truck, Coupe, Van, etc.)
`condition`	No	Vehicle condition: "used", "new", or "certified". Comma-separated to combine (e.g. "used,certified"). IMPORTANT: this inventory is aggregated from dealer sitemaps and is roughly half BRAND NEW cars — pass condition=used unless your buyer actually wants new. Omitting this returns both.
`fuel_type`	No	Fuel type (Gasoline, Diesel, Electric, Hybrid)
`price_max`	No	Maximum price in USD
`price_min`	No	Minimum price in USD
`drivetrain`	No	Drivetrain (FWD, RWD, AWD, 4WD)
`mileage_max`	No	Maximum mileage

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 2, 2026

addedInput schema / properties / condition

Added value: +{
+  "description": "Vehicle condition: \"used\", \"new\", or \"certified\". Comma-separated to combine (e.g. \"used,certified\"). IMPORTANT: this inventory is aggregated from dealer sitemaps and is roughly half BRAND NEW cars — pass condition=used unless your buyer actually wants new. Omitting this returns both.",
+  "type": "string"
+}

Changed1 schema field changedSep 2, 2026

addedInput schema / properties / agent_id

Added value: +{
+  "description": "Your agent identifier (claude, grok, gpt, perplexity)",
+  "type": "string"
+}

First observedMay 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full burden and it delivers: it clearly flags the data aggregation source (dealer sitemaps), the roughly half new-car composition, the condition semantics, and that every result states its condition. This goes well beyond the input schema and gives the agent essential behavioral context for interpreting results.

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 compact and front-loaded: the core action and resource appear first, followed by filters, then the critical caveat. Every sentence adds information not otherwise obvious from the schema, and the condition warning is placed prominently without being buried.

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

Completeness5/5

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

Given 17 optional parameters, no required fields, no output schema, and no annotations, the description provides sufficient guidance to invoke the tool correctly. It covers scope, key caveats, and result content. Pagination is documented in the schema (offset/limit), and every result condition disclosure is stated. No critical operational gap remains.

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 17 parameters. The description adds aggregate context and emphasizes the critical condition parameter, but does not need to repeat each filter's meaning. Baseline 3 is appropriate.

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

Purpose5/5

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

Description begins with a specific verb and resource: 'Search vehicle inventory across all dealers.' It lists many filter dimensions and explicitly distinguishes that results include dealer info. It is clearly differentiated from siblings like cars_dealer_inventory and cars_vehicle by the aggregate multi-dealer search scope.

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

Usage Guidelines5/5

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

Provides explicit operational guidance: the inventory contains both new and used cars, and instructs to pass condition="used" to exclude new unless the buyer wants new. This directly tells the agent when and how to adjust parameters, which is especially valuable given 17 optional filters and no required parameters.

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

All marketplace tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?