Skip to main content
Glama

CarsDirect used-car listings near a US ZIP code: vehicle

auto_carsdirect_vehicle
Read-only

CarsDirect used-car listings near a US ZIP code (optionally one make and model): vehicle name, year, make, model, condition, mileage, exterior and interior colour, price (USD), dealer name with distance, photo and listing link, about 20-25 per page. From carsdirect.com via a residential proxy. Takes 13 to 25 s; allow a 45 s timeout. Related tools on this server, for a different need: auto_fipe_brazil_vehicle_prices when you need Brazilian FIPE reference price for one car: brand, model; auto_data_wa_gov_electric_vehicle when you need Washington State Department of Licensing registered. Price: $0.02 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "zip": "<zip>"
    },
    "name": "auto_carsdirect_vehicle"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYesUS ZIP code, e.g. 90210
makeNoOptional make slug, e.g. honda, ford, toyota
pageNoResult page 1-10 (default 1)
modelNoOptional model slug (needs make), e.g. civic, f-150

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses residential-proxy sourcing, latency (13-25 s), required 45 s timeout, ~20-25 results per page, and a per-call price with x402 payment networks and a no-charge-on-failure policy. These are exactly the operational facts an agent cannot get from annotations.

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 purpose, then constraints, then alternatives, then pricing — a sensible order with no filler sentences. The enumeration of every returned field is somewhat redundant given an output schema exists, but it stays compact.

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?

For an open-world, proxied scraping tool with a payment model, the description covers timing, timeout, cost, payment mechanism, failure billing, result volume, and pagination. With an output schema already defining the return shape, nothing an agent needs to call this safely 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 description coverage is 100%, so zip, make, model, and page are already documented, including that model requires make. The description only restates 'optionally one make and model' and adds no syntax, slug format, or page-bound guidance beyond the schema, so the baseline 3 applies.

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?

The description states a specific verb and resource ('CarsDirect used-car listings near a US ZIP code') plus the returned fields and pagination size, so an agent knows exactly what it retrieves. It also distinguishes itself from the named siblings (FIPE prices, WA DOL registrations) by need.

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

Usage Guidelines4/5

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

It gives an explicit routing rule: 'Related tools on this server, for a different need' followed by the two alternatives and the condition that selects each. It lacks an explicit exclusion for when a user wants new cars or a different marketplace, but the 'used-car' framing and named alternatives give clear context.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources