OmniaAuto — Canadian Vehicle Listings

market_stats

Read-only

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

Market statistics for any slice of Canadian vehicle listings: vehicle counts, average/median price and mileage, with optional group_by breakdowns. Use it for price and supply questions across many vehicles; use valuation for one year/make/model estimate, search_listings to see individual vehicles and coverage for the dataset's overall size. An invalid condition, group_by, sort, near or radius_km returns an error and costs nothing.

Input Schema

TableJSON Schema

Name	Required	Description
`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	n = largest groups first (default); sold_30d = most sold in 30 days, needs group_by and condition Used or New
`model`	No	Model, e.g. RAV4; exact match, any case
`group_by`	No	Up to 2 of city, trim, year, condition, model (largest 25 groups, rest as Other); city needs province or near, trim needs make and model
`province`	No	2-letter province code, e.g. AB, ON, QC; empty = all Canada
`year_max`	No	Latest model year, e.g. 2024; 0 = any
`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
`radius_km`	No	Radius around near, in km (default 25, max 500); requires near

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
`detail`	No
`groups`	No	One object per group, with n and price figures
`allowed`	No	Accepted values, on an invalid_* error
`pricing`	No
`summary`	No	n, unique_vins, avg_price, median_price, min_price, max_price, avg_mileage, priced
`group_by`	No	Breakdown dimensions applied
`by_province`	No
`by_condition`	No
`by_certification`	No
`credits_remaining`	No	Credits left in the current period

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 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 / condition / description

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

changedInput schema / properties / group_by / description

Previous value: -"Breakdown: city, trim, year, condition or model"New value: +"Up to 2 of city, trim, year, condition, model (largest 25 groups, rest as Other); city needs province or near, trim needs make and model"

changedInput schema / properties / make / description

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

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 / 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: -"n (default) or sold_30d"New value: +"n = largest groups first (default); sold_30d = most sold in 30 days, needs group_by and condition Used or New"

changedInput schema / properties / year_max / description

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

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": {
+    "allowed": {
+      "description": "Accepted values, on an invalid_* error",
+      "items": {},
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "by_certification": {
+      "additionalProperties": true,
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "by_condition": {
+      "items": {},
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "by_province": {
+      "items": {},
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "credits_remaining": {
+      "description": "Credits left in the current period",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "detail": {
+      "type": [
+        "string",
+        "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"
+      ]
+    },
+    "group_by": {
+      "description": "Breakdown dimensions applied",
+      "items": {},
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "groups": {
+      "description": "One object per group, with n and price figures",
+      "items": {},
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "pricing": {
+      "additionalProperties": true,
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "summary": {
+      "additionalProperties": true,
+      "description": "n, unique_vins, avg_price, median_price, min_price, max_price, avg_mileage, priced",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "unit": {
+      "description": "Always vehicle",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing the cost model (1 credit per call, out_of_credits at zero balance) and the failure semantics (invalid condition, group_by, sort, near or radius_km errors and costs nothing). It does not add much on the read-only/idempotency side, but the annotations already cover that profile and the credit/error behavior is genuinely new information.

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?

Cost is front-loaded in a dedicated labeled sentence, and the usage routing follows immediately. Two dense paragraphs; the description is slightly long but every sentence carries either cost, scope, routing or error behavior.

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?

Output schema exists, so return values need no explanation, and the description still supplies cost, error implications, filtering scope and sibling routing for an 11-parameter tool. Nothing an agent needs to call it correctly is missing.

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 11 parameters including defaults and constraints like radius_km's 25/500 bounds. The description only alludes to group_by breakdowns and lists the condition/group_by/sort/near/radius_km parameters as error sources, which adds marginal value over the schema.

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+resource: market statistics for Canadian vehicle listings, enumerating the exact metrics returned (counts, average/median price and mileage) plus group_by breakdowns. An agent can distinguish it from valuation, search_listings and coverage 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?

Explicitly names the alternative for each case: valuation for a single year/make/model estimate, search_listings for individual vehicles, coverage for overall dataset size, and this tool for price/supply questions across many vehicles. Nothing is left to inference.

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?