OmniaAuto — Canadian Vehicle Listings

valuation

Read-only

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

Price estimate (low/average/median/high) for one year, make, model and condition, from recent Canadian comparables, with province and mileage breakdowns. Use it for what a specific car is worth; use market_stats for market-wide figures and search_listings for individual vehicles. No comparables returns empty figures and a note, not an error; an invalid condition or a free-plan key returns an error (invalid_condition, upgrade_required) and costs nothing.

Input Schema

TableJSON Schema

Name	Required	Description
`make`	Yes	Make, e.g. Toyota; any case
`trim`	No	Trim, e.g. XLE, to narrow the estimate; empty = all trims
`year`	Yes	Model year, e.g. 2020
`model`	Yes	Model, e.g. RAV4; a common alternate spelling is resolved
`mileage`	No	Odometer in km; compares similar-mileage cars (band widened if few); 0 = ignore mileage
`province`	No	2-letter province code, e.g. AB, ON, QC; empty = all Canada
`condition`	Yes	New, Used, Certified or Demo (required)

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`error`	No	Set on a refusal, e.g. out_of_credits, not_found; result fields are then absent
`notes`	No	Caveats to relay with the figures
`query`	No	The year, make, model, condition, province, trim and mileage priced
`detail`	No
`allowed`	No	Accepted values, on an invalid_* error
`valuation`	No	low, average, median, high (CAD), sample_size, avg_mileage, mileage_band
`confidence`	No	low, medium or high, from the sample size
`sold_comps`	No
`by_province`	No
`total_comps`	No	Comparables found
`window_days`	No	Age of the comparables window, days
`by_mileage_band`	No
`credits_remaining`	No	Credits left in the current period
`by_province_mileage_band`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 17, 2026

changedInput schema / properties / condition / description

Previous value: -"New, Used, Certified or Demo"New value: +"New, Used, Certified or Demo (required)"

changedInput schema / properties / make / description

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

changedInput schema / properties / mileage / description

Previous value: -"Odometer, km"New value: +"Odometer in km; compares similar-mileage cars (band widened if few); 0 = ignore mileage"

changedInput schema / properties / model / description

Previous value: -"Model, e.g. RAV4"New value: +"Model, e.g. RAV4; a common alternate spelling is resolved"

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 / trim / description

Previous value: -"Trim"New value: +"Trim, e.g. XLE, to narrow the estimate; empty = all trims"

changedInput schema / properties / year / description

Previous value: -"Model year"New value: +"Model year, e.g. 2020"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "allowed": {
+      "description": "Accepted values, on an invalid_* error",
+      "items": {},
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "by_mileage_band": {
+      "items": {},
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "by_province": {
+      "items": {},
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "by_province_mileage_band": {
+      "items": {},
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "confidence": {
+      "description": "low, medium or high, from the sample size",
+      "type": [
+        "string",
+        "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"
+      ]
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "notes": {
+      "description": "Caveats to relay with the figures",
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "query": {
+      "additionalProperties": true,
+      "description": "The year, make, model, condition, province, trim and mileage priced",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "sold_comps": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "total_comps": {
+      "description": "Comparables found",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "valuation": {
+      "additionalProperties": true,
+      "description": "low, average, median, high (CAD), sample_size, avg_mileage, mileage_band",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "window_days": {
+      "description": "Age of the comparables window, days",
+      "type": [
+        "integer",
+        "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 this a safe read, but the description goes well beyond them: 1 credit per call, balance visible via my_usage, out_of_credits at zero, empty figures plus a note (not an error) when there are no comparables, and invalid_condition/upgrade_required errors that cost nothing. That is exactly the failure-mode detail an agent needs and cannot get from structured fields.

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 and the routing rule follows, so the most actionable facts come first. The parenthetical about OmniaAuto credits and my_usage is slightly dense, but no sentence is filler.

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?

A 7-parameter required-4 tool with full schema descriptions, annotations, and an output schema — the description covers the remaining gaps (credits, error semantics, empty-result behavior) so 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.

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; the description still adds value by explaining that province and mileage drive breakdowns in the output and that the estimate is built from recent Canadian comparables. It does not add meaning for trim, which the schema already covers.

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 concrete verb and resource — a low/average/median/high price estimate for one year/make/model/condition from recent Canadian comparables — and names two siblings it is not (market_stats, search_listings). An agent can distinguish it from every sibling without opening a 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 selection rule: 'use it for what a specific car is worth; use market_stats for market-wide figures and search_listings for individual vehicles.' It also states the cost model and when a call does or does not consume credits.

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?