Skip to main content
Glama

Search used cars for sale in Spain

search_cars
Read-only

Used cars for sale at Spanish dealers right now, each with its price against the usual price of comparable cars (cheap, fair or expensive) and the page to see it. Turn the user's request into the filters: words for make, model, version or fuel go in query ("Toyota Corolla híbrido"), and price, year, mileage and province in their own fields. Results come cheapest against the market first unless sort says otherwise.

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": "search_cars"
  }
}

Input Schema

NameRequiredDescriptionDefault
fuelNoOptional: Gasolina, Diésel, Híbrido, Híbrido enchufable, Eléctrico, GLP or GNC
sortNomarket (cheapest against its market first, the default), price, year (newest first) or km
limitNoHow many cars, 1 to 20; 8 if not given
queryNoMake, model, version or fuel words, e.g. "Golf GTI"
max_kmNoMost kilometres, optional
min_yearNoOldest year of registration, optional
provinceNoSpanish province, optional
max_priceNoHighest asking price in euros, optional
min_priceNoLowest asking price in euros, optional

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already establish this is a read-only, closed-world lookup, and the description usefully adds that listings are current ('right now'), that each result is benchmarked against comparable cars, and that default ordering is best-against-market. Beyond that it says nothing about rate limits, result freshness windows, or what happens when no cars match — context that would matter for a live-marketplace query.

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 what the tool returns before the parameter-mapping instructions, with no filler. The middle sentence is dense but each clause carries a distinct instruction; only a touch of tightening would make it a 5.

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 nine-parameter optional-filter search with no output schema, the definition covers purpose, filter mapping, default sort and the shape of the returned data (price verdict plus page link). Pagination and empty-result behavior are unaddressed, but nothing essential to calling it correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description earns above that by clarifying the overlap the schema leaves implicit — that fuel words may go into query as well as the dedicated fuel field, and that ordering follows market-relative price unless sort overrides. It never touches limit or the price range semantics, but those are self-evident from the schema.

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 concrete verb+resource+scope: 'Used cars for sale at Spanish dealers right now', and explains what each result carries (price vs. comparable cars, page link). It is instantly distinguishable as a listing search, but it never names or contrasts the sibling tools (check_price, province_market), so an agent must infer the boundary rather than being told it.

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 explicit routing guidance for the main ambiguity: free-text make/model/version/fuel words belong in query, while price, year, mileage and province go in their own fields. What is missing is any when-not-to-use signal or pointer to check_price for a single listing's price, so the agent is left to guess the boundary with siblings.

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