Skip to main content
Glama

Carfinity car marketplace

Search cars for sale

search_cars
Read-onlyIdempotent

Search new and used cars for sale at local dealers, in plain language. Every car comes back with its advertised price, its market price, how far under or over market it is, a deal label, a 0 to 100 score and its rank among comparable cars. Use a market name in the query or the market argument. Returns up to 10 cars per call, best deals first.

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": {
      "query": "<query>"
    },
    "name": "search_cars"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage of results, 10 cars each.
sortNoOrder of results.best
queryYesWhat the shopper wants, in their words. Examples: 'used SUV under $30k AWD', 'new Honda CR-V', 'certified Toyota under 40,000 miles', 'something cheap on gas for commuting'.
marketNoMarket slug from list_markets, for example 'dallas-tx'. Optional if the query names the city.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive) and openness, so the description correctly spends its words elsewhere: it discloses the per-car payload (advertised price, market price, delta, deal label, 0-100 score, rank), the 10-result cap, and the default ordering (best deals first). That is meaningful context an agent cannot get from the annotations, though rate limits and whether results are cached are unstated.

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?

Three sentences, front-loaded with purpose, then return shape, then the market scoping rule and result cap. Every sentence carries information, though the market sentence partially duplicates what the schema already says about the optional city reference.

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?

With no output schema, the description carries the burden of describing returns and does so concretely: field list, deal label, score, rank, count cap, and ordering. Combined with the fully covered input schema and safety annotations, an agent has everything needed to call this correctly.

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 query, market, page, and sort are all already documented, including the note that market is optional when the query names a city. The description's market guidance largely restates that, adding no new syntax or format detail, so the baseline 3 applies.

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 opens with a specific verb and resource ("Search new and used cars for sale at local dealers") and adds a distinguishing modality ("in plain language"), so an agent knows this is a natural-language inventory search. It does not explicitly contrast itself with siblings like compare_cars or get_car, which keeps it short of a 5.

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?

Guidance is present but narrow: "Use a market name in the query or the market argument" tells the agent how to scope results, and "in plain language" implies free-text queries are expected. There is no statement of when to prefer compare_cars or get_car, and no exclusions or prerequisites, so usage is implied rather than prescribed.

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