OmniaAuto — Canadian Vehicle Listings

search_listings

Read-only

COST: 3 credits per call (OmniaAuto credits; my_usage shows the balance; at zero a call returns out_of_credits).

Search live Canadian vehicle listings by make, model, location, price and other filters: returns up to 10 matching vehicles (specs, price, mileage, location, listing_url) and the total count. Use it to see individual vehicles, not market-wide figures (market_stats) or a price estimate (valuation). Show listing_url to the user (null means no link, never invent one); an unrecognised condition, near or radius_km returns an error and costs nothing.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	City name, e.g. Calgary; exact match, any case
`make`	No	Make, e.g. Toyota; exact match, any case
`near`	No	Centre of a radius search: city, postal code or lat,lng (e.g. 53.54,-113.49); radius_km sets its size
`sort`	No	price, mileage, year, last_seen (default), first_seen or distance (requires near)
`limit`	No	Vehicles to return, 1-10; larger values are capped at 10
`model`	No	Model, e.g. RAV4; exact match, any case
`order`	No	asc or desc; default is asc for price, mileage and distance, desc otherwise
`province`	No	2-letter province code, e.g. AB, ON, QC; empty = all Canada
`year_min`	No	Earliest model year, e.g. 2020; 0 = any
`body_type`	No	SUV, Sedan, Pickup, Hatchback, Minivan, Coupe, Van, Convertible or Wagon; empty = any
`condition`	No	New, Used, Certified or Demo; empty = any
`price_max`	No	Max price in CAD; 0 = no limit
`price_min`	No	Min price in CAD; 0 = no limit
`radius_km`	No	Radius around near, in km (default 25, max 500); requires near
`mileage_max`	No	Max odometer in km; 0 = no limit

Output Schema

TableJSON Schema

Name	Required	Description
`geo`	No	Resolved near anchor and radius_km, on a radius search
`note`	No
`unit`	No	Always vehicle
`error`	No	Set on a refusal, e.g. out_of_credits, not_found; result fields are then absent
`total`	No	Vehicles matching the filters
`results`	No	One object per vehicle: vin, MY, Make, model, Trim, Condition, mileage, price, City, Province, listing_url, distance_km on a radius search
`returned`	No	Vehicles in results
`total_exact`	No
`pricing_note`	No
`credits_remaining`	No	Credits left in the current period
`allowance_exhausted`	No	True when the plan's vehicle limit is reached: total is returned, results is empty

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedOct 17, 2026

changedInput schema / properties / body_type / description

Previous value: -"e.g. SUV, Sedan, Pickup"New value: +"SUV, Sedan, Pickup, Hatchback, Minivan, Coupe, Van, Convertible or Wagon; empty = any"

changedInput schema / properties / city / description

Previous value: -"City name"New value: +"City name, e.g. Calgary; exact match, any case"

changedInput schema / properties / condition / description

Previous value: -"New, Used, Certified or Demo"New value: +"New, Used, Certified or Demo; empty = any"

changedInput schema / properties / limit / description

Previous value: -"Max vehicles to return"New value: +"Vehicles to return, 1-10; larger values are capped at 10"

changedInput schema / properties / make / description

Previous value: -"Make, e.g. Toyota"New value: +"Make, e.g. Toyota; exact match, any case"

changedInput schema / properties / mileage_max / description

Previous value: -"Max mileage, km"New value: +"Max odometer in km; 0 = no limit"

changedInput schema / properties / model / description

Previous value: -"Model, e.g. RAV4"New value: +"Model, e.g. RAV4; exact match, any case"

changedInput schema / properties / near / description

Previous value: -"City, postal code or lat,lng"New value: +"Centre of a radius search: city, postal code or lat,lng (e.g. 53.54,-113.49); radius_km sets its size"

changedInput schema / properties / order / description

Previous value: -"asc or desc"New value: +"asc or desc; default is asc for price, mileage and distance, desc otherwise"

changedInput schema / properties / price_max / description

Previous value: -"Max price, CAD"New value: +"Max price in CAD; 0 = no limit"

changedInput schema / properties / price_min / description

Previous value: -"Min price, CAD"New value: +"Min price in CAD; 0 = no limit"

changedInput schema / properties / province / description

Previous value: -"Province, e.g. AB"New value: +"2-letter province code, e.g. AB, ON, QC; empty = all Canada"

changedInput schema / properties / radius_km / description

Previous value: -"Radius around near, km (default 25, max 500)"New value: +"Radius around near, in km (default 25, max 500); requires near"

changedInput schema / properties / sort / description

Previous value: -"price, mileage, year, last_seen, first_seen or distance"New value: +"price, mileage, year, last_seen (default), first_seen or distance (requires near)"

changedInput schema / properties / year_min / description

Previous value: -"Earliest model year"New value: +"Earliest model year, e.g. 2020; 0 = any"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "allowance_exhausted": {
+      "description": "True when the plan's vehicle limit is reached: total is returned, results is empty",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "credits_remaining": {
+      "description": "Credits left in the current period",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "error": {
+      "description": "Set on a refusal, e.g. out_of_credits, not_found; result fields are then absent",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "geo": {
+      "additionalProperties": true,
+      "description": "Resolved near anchor and radius_km, on a radius search",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "pricing_note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "results": {
+      "description": "One object per vehicle: vin, MY, Make, model, Trim, Condition, mileage, price, City, Province, listing_url, distance_km on a radius search",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "returned": {
+      "description": "Vehicles in results",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "total": {
+      "description": "Vehicles matching the filters",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "total_exact": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "unit": {
+      "description": "Always vehicle",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds the non-obvious economics and failure modes instead of repeating them. It discloses the 3-credit cost, that my_usage shows the balance, the out_of_credits return at zero balance, and that an unrecognised condition, near or radius_km errors out and costs nothing.

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, each load-bearing, with the highest-stakes fact (credit cost) front-loaded. Slightly dense in the middle sentence, where filter and return detail run together, but there is no filler and nothing is repeated from the schema.

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 a 15-parameter, zero-required search tool with an output schema present, the description covers everything the schema and annotations do not: cost, credit exhaustion, error-and-no-charge behavior, link handling, and sibling routing. No gaps remain that would cause a mis-call.

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 100%, so the per-parameter syntax is already carried by the schema and the baseline would be 3. The description adds validation semantics the schema does not state: unrecognised values for condition, near and radius_km produce an error, and null listing_url means no link rather than a fabricated one.

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 live Canadian vehicle listings') plus the filter dimensions and the exact return shape (up to 10 vehicles with specs, price, mileage, location, listing_url, plus total count). It explicitly names the two siblings it is not (market_stats, valuation), so an agent can route without opening any schema.

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?

Gives an explicit when-to-use rule ('Use it to see individual vehicles') and an explicit when-not, naming the alternatives market_stats for market-wide figures and valuation for a price estimate. It also states the operator-side constraint that listing_url must be shown and never invented.

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

All OmniaAuto — Canadian Vehicle Listings 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?