OmniaAuto — Canadian Vehicle Listings

Vehicle Valuation

valuation

Read-only

COST: 1 credit per call.

Returns a low, average, median and high price estimate for one year, make, model and condition from recent Canadian comparable listings, with province and mileage breakdowns.

Input 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)
`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
`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.

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"
+}

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

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only, non-destructive and closed-world behaviour, so the description rightly focuses on things annotations cannot express: the 1-credit cost per call, the Canadian comparable-listing data source, and the shape of the returned price bands with province/mileage breakdowns. It does not say what happens when no comparables exist, which is the main remaining gap.

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?

Two sentences with no wasted words, and the cost constraint is front-loaded where an agent will see it first. The second sentence is dense but every clause (price bands, data source, breakdowns) carries information.

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 an output schema present, the description need not explain return values, and annotations cover the safety profile; what remains for the description — cost, data provenance, and the price-band summary — is fully provided. An agent has everything needed to decide to call it and interpret the result set.

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 every parameter is already documented in detail (trim narrowing, mileage banding, province codes, seller_type segmentation). The description only restates year/make/model/condition and adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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 names a specific output (low, average, median and high price estimate) for a specific input (one year/make/model/condition) drawn from recent Canadian comparable listings. That is enough to separate it from search_listings or market_stats, though it never explicitly names those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the single-vehicle pricing tool and the others are not, but there is no explicit 'use this when…' statement, no mention of when market_stats or search_listings is the better call, and no guidance on prerequisites.

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?