OmniaAuto — Canadian Vehicle Listings

Search Listings

search_listings

Read-only

COST: 3 credits per call.

Returns up to 10 live Canadian vehicle listings matching the filters (specs, price, mileage, location, listing_url) and the total match count.

Input 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
`seller_type`	No	dealer (default) or private: private-seller listings, a separate segment (seller Private, city and province only, no link or VIN)

Output 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.

Changed1 schema field changedNov 4, 2026

addedInput schema / properties / seller_type

Added value: +{
+  "default": "",
+  "description": "dealer (default) or private: private-seller listings, a separate segment (seller Private, city and province only, no link or VIN)",
+  "title": "Seller Type",
+  "type": "string"
+}

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

A3.6/5.0

Behavior4/5

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

Annotations already cover read-only, non-destructive, closed-world behavior. The description adds meaningful context beyond those annotations by disclosing the 3-credit cost per call, the 10-listing cap, and the total match count return behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences and front-loads the cost, then explains the result size and content. Every sentence carries useful information with no wasted wording.

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 16-parameter search tool, the description plus the fully documented schema and existing output schema give the agent enough to invoke it correctly. The main gap is the absence of sibling-tool routing guidance, not missing parameter or return details.

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 schema already documents all 16 parameters in detail. The description only groups them into categories such as specs, price, mileage, and location, adding little parameter-level meaning beyond 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 clearly states the resource and scope: up to 10 live Canadian vehicle listings matching filters, plus total match count. It does not explicitly differentiate from siblings such as valuation or market_stats, so it falls just 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus the available alternatives like valuation or market_stats. The description only covers cost and return shape, leaving usage context to inference from the name and schema.

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?