OmniaAuto — Canadian Vehicle Listings

coverage

Read-only

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

Dataset size: the number of distinct vehicles currently listed in Canada, the number of brands and the last update date. Use it for how big the dataset is; use market_stats for counts of a specific make, model or area.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`unit`	No	Always vehicle
`error`	No	Set on a refusal, e.g. out_of_credits, not_found; result fields are then absent
`brands`	No	Number of makes
`vehicles`	No	Distinct vehicles currently listed
`latest_update`	No	Date of the latest data update, YYYY-MM-DD
`credits_remaining`	No	Credits left in the current period

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "brands": {
+      "description": "Number of makes",
+      "type": [
+        "integer",
+        "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"
+      ]
+    },
+    "latest_update": {
+      "description": "Date of the latest data update, YYYY-MM-DD",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "unit": {
+      "description": "Always vehicle",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "vehicles": {
+      "description": "Distinct vehicles currently listed",
+      "type": [
+        "integer",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations declare this a non-destructive, closed-world read, and the description adds real behavioral context those hints do not carry: 1 credit per call, the my_usage balance reference, and the concrete failure mode (out_of_credits at zero). This billing and quota behaviour is exactly the kind of operational detail an agent cannot infer from the annotations.

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?

Two compact statements, with the cost constraint front-loaded before the capability and sibling routing. Every clause carries information the agent needs; nothing is padding.

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 zero-parameter, read-only dataset summary with an output schema, the description covers cost, scope, return content, and the alternative tool. The output schema handles return-shape detail, so nothing material 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. It correctly implies a parameterless call rather than leaving the agent wondering what inputs are needed.

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?

The description names a specific resource and scope: the number of distinct vehicles listed in Canada, the brand count, and the last-update date. It also explicitly distinguishes the tool from market_stats, so an agent can tell the two apart without opening either 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?

It gives a direct routing rule: use this tool for how big the dataset is, and use market_stats for counts of a specific make, model, or area. There is no ambiguity left about which sibling to pick.

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?