Skip to main content
Glama

CARFAX used-car listings by body style or price ceiling

auto_carfax
Read-only

CARFAX used-car listings by body style or price ceiling (optionally near a US ZIP): total matches and 24 cars per page with VIN, year, make, model, trim, mileage, price, value badge, history flags (one owner, no accidents, service history), colour, drivetrain, engine, fuel, MPG, dealer, rating, location, phone, photo and link. From carfax.com via a stealth proxy. Takes about 10 s; allow a 30 s timeout. Related tools on this server, for a different need: auto_carsdirect_vehicle when you need CarsDirect used-car listings near a US ZIP code: vehicle; auto_fipe_brazil_vehicle_prices when you need Brazilian FIPE reference price for one car: brand, model. Price: $0.03 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "auto_carfax"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNoOptional US ZIP code to search near
pageNoResult page 1-50 (default 1)
bodyTypeNosuv, sedan, pickup, coupe, convertible, hatchback, minivan, wagon (or use maxPrice)
maxPriceNoPrice ceiling instead of body type: 1000, 2000, 3000, 4000, 5000, 10000, 15000, 20000, 25000, 30000, 35000, 50000

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses meaningful behavior: results come from carfax.com via a stealth proxy, the call takes about 10 seconds with a suggested 30-second timeout, pagination returns 24 cars per page, and pricing is $0.03 per successful call with no charge for failures. These are exactly the operational details an agent needs before invoking the tool.

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?

The purpose is front-loaded, and the description is organized into purpose, result contents, latency, alternatives, and pricing without filler. It is somewhat dense and enumerates many returned fields even though an output schema exists, which adds minor redundancy, but the wording remains serviceable and clear.

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 an output schema and annotations, the description is complete for correct invocation and expectation-setting: it covers source, proxy behavior, timing, pagination, cost, failure charging, and sibling alternatives. An agent has enough information to decide to use it and to call it with a reasonable timeout.

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 input schema already documents zip, page, bodyType, and maxPrice, including the body-type/maxPrice alternative. The description adds useful context about total matches and 24 results per page, but it does not add parameter-specific syntax or constraints beyond the schema, so the baseline of 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?

The description states a specific resource and scope: CARFAX used-car listings filtered by body style or price ceiling, optionally near a US ZIP. It also explicitly distinguishes this tool from CarsDirect listings and Brazilian FIPE price lookup, so an agent can identify the right tool without opening sibling schemas.

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?

It names concrete alternatives and the conditions that select them: use auto_carsdirect_vehicle for CarsDirect used-car listings near a ZIP, and auto_fipe_brazil_vehicle_prices for Brazilian FIPE reference prices. The opening phrase also makes the primary use case clear: CARFAX listings by body style or price ceiling.

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