PegaRex

Search vehicle listings

search_vehicles

Read-onlyIdempotent

Search 1.8M+ Brazilian vehicle listings aggregated from 96 platforms (OLX, Webmotors, Napista, etc.). Returns listings with price, year, mileage, location, source platform, the original ad URL, FIPE reference price and a deal_score (% vs FIPE; negative means priced below FIPE).

A car listed on several sites comes back once (vehicle_sites says how many sites carry
it); filtering by `source` returns that site's own ads instead. price_kind is set when
the asking price is not the car's sale price ("installment": a monthly installment or
down payment posted as the price; "equity": ágio, the buyer takes over a financing;
"suspect" / "outlier_high": check the ad) — never present such a price as a bargain.

Tips for best results:
- Free-text `query` matches the listing TITLE only (e.g. "Onix LTZ turbo").
  It needs at least one word of 3+ characters: "Ford Ka", not "Ka" alone.
- For exact brand/model/version filtering, resolve names to ids first with
  list_brands / list_models / list_versions and pass brand_id/model_id/
  version_id — it is faster and more accurate than the text fields.
- `location` is a 2-letter UF (e.g. "SP") or a city name.
- `sort_by="newest"` (default) lists the most recently LISTED cars first —
  the date a listing first appeared on its source, not when we last saw it.
- `sort_by="best_deal"` ranks by lowest price-to-FIPE ratio.
- `per_page` is capped at 50. Use `page` (1-20) to paginate; past the first
  20 pages, narrow the search with filters. `total_count` and
  `total_pages` are returned.

Input Schema

TableJSON Schema

Name	Required	Default
`page`	No
`brand`	No
`model`	No
`query`	No
`source`	No
`sort_by`	No	newest
`version`	No
`brand_id`	No
`category`	No	Cars
`location`	No
`model_id`	No
`per_page`	No
`year_max`	No
`year_min`	No
`fuel_type`	No
`price_max`	No
`price_min`	No
`body_style`	No
`version_id`	No
`mileage_max`	No
`mileage_min`	No
`transmission`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedOct 6, 2026

changedInput schema / properties / body_style / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 80,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / brand / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 80,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / brand_id / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9223372036854776000,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / location / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 80,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / mileage_max / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9223372036854776000,
+    "minimum": -9223372036854776000,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / mileage_min / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9223372036854776000,
+    "minimum": -9223372036854776000,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / model / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 80,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / model_id / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9223372036854776000,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / page / maximum
```
Added value: +9223372036854776000
```
addedInput schema / properties / page / minimum
```
Added value: +-9223372036854776000
```
addedInput schema / properties / per_page / maximum
```
Added value: +9223372036854776000
```
addedInput schema / properties / per_page / minimum
```
Added value: +-9223372036854776000
```

changedInput schema / properties / price_max / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9223372036854776000,
+    "minimum": -9223372036854776000,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / price_min / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9223372036854776000,
+    "minimum": -9223372036854776000,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / query / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 100,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / source / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 80,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / version / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 80,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / version_id / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9223372036854776000,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / year_max / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9223372036854776000,
+    "minimum": -9223372036854776000,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / year_min / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9223372036854776000,
+    "minimum": -9223372036854776000,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

First observedSep 25, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds substantial behavior the agent could not infer: de-duplication across sites with vehicle_sites counts, the effect of `source` on that dedup, the meaning of price_kind values (installment/equity/suspect/outlier_high) with a warning never to present such prices as bargains, and the per_page/page caps.

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-loads what the tool is and returns before the 'Tips for best results' block; bullets map one idea per line with no filler. The length is justified by 22 undocumented parameters, though the section could be marginally tighter.

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 fully covers return values (fields plus deal_score definition and sign convention) and with no schema param descriptions it covers the parameters most at risk of misuse. Combined with the annotations, an agent has everything needed to call and interpret results correctly.

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 description coverage is 0%, so the description carries the burden and does so for the ambiguous params: `query` (title-only, 3+ char minimum), id-based vs text brand/model/version, `location` as a 2-letter UF or city, `sort_by` values, `per_page` cap and `page` range, and `source`. Several filters (price_min/max, year_min/max, mileage_min/max, fuel_type, transmission, body_style, category) are left unexplained, but they are largely self-describing enumerations/int ranges.

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?

States a specific verb and resource ('Search ... Brazilian vehicle listings') plus concrete scope (1.8M listings, 96 platforms, named sources). It describes the returned record shape (price, year, mileage, FIPE reference, deal_score) and dedup behavior, so it is clearly distinguishable from siblings like get_vehicle_by_id or get_listing_details.

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?

Explicit routing guidance: use free-text `query` only for title matching, and resolve exact brand/model/version to ids via list_brands/list_models/list_versions because it is 'faster and more accurate.' It also documents sorting semantics, pagination limits, and the advice to narrow with filters past page 20 — real when-to-use and when-not-to inference.

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

All PegaRex 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?