OmniaAuto — Canadian Vehicle Listings

get_vin

Read-only

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

Get the latest live listing for one VIN: price, mileage, location and listing_url. Use it when you have a VIN and want that vehicle's listing; use decode_vin for the specs of any VIN, listed or not, and search_listings to find vehicles without a VIN. Show listing_url to the user (null means no link, never invent one); a VIN with no live listing returns error not_found.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`vin`	Yes	17-character VIN, letters and digits without I, O or Q; any case

Output Schema

TableJSON Schema

Name	Required	Description
`MY`	No	Model year
`vin`	No
`City`	No
`Make`	No
`Trim`	No
`note`	No
`error`	No	Set on a refusal, e.g. out_of_credits, not_found; result fields are then absent
`model`	No
`price`	No	Asking price, CAD; null when none is advertised
`mileage`	No	Odometer, km
`Province`	No
`Condition`	No
`listing_url`	No	Link to show the user; null means no link
`credits_remaining`	No	Credits left in the current period

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 17, 2026

changedInput schema / properties / vin / description

Previous value: -"17-character VIN"New value: +"17-character VIN, letters and digits without I, O or Q; any case"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "City": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "Condition": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "MY": {
+      "description": "Model year",
+      "type": [
+        "integer",
+        "string",
+        "null"
+      ]
+    },
+    "Make": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "Province": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "Trim": {
+      "type": [
+        "string",
+        "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"
+      ]
+    },
+    "listing_url": {
+      "description": "Link to show the user; null means no link",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "mileage": {
+      "description": "Odometer, km",
+      "type": [
+        "integer",
+        "number",
+        "null"
+      ]
+    },
+    "model": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price": {
+      "description": "Asking price, CAD; null when none is advertised",
+      "type": [
+        "integer",
+        "number",
+        "null"
+      ]
+    },
+    "vin": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly/openWorld/destructive/idempotent), and the description layers on top: cost of 1 credit per call, the credit-exhaustion failure mode (out_of_credits with my_usage as the balance check), the null listing_url convention with an explicit 'never invent one' instruction, and the not_found error path. This is behavior an agent cannot infer 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.

Conciseness5/5

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

Three sentences, front-loaded with the cost constraint an agent needs before calling, then purpose, then routing and edge cases. No sentence is redundant and the most decision-relevant information (credits) leads.

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, return-value structure need not be restated, and the description instead spends its budget on cost, error modes, and alternate-tool routing. For a single-parameter read tool this leaves no material gap.

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% and the single vin parameter already documents the 17-character format and the I/O/Q exclusion. The description adds no format, normalization, or validation detail beyond the schema, so the baseline 3 is the correct ceiling here.

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 opens with a concrete verb+resource — 'Get the latest live listing for one VIN' — and enumerates the returned fields (price, mileage, location, listing_url). It explicitly separates itself from decode_vin and search_listings, so an agent can pick the right tool without inspecting 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?

It states the selecting condition ('when you have a VIN and want that vehicle's listing') and names both alternatives with the conditions that route to them: decode_vin for specs of any VIN, search_listings to find vehicles without a VIN. The not_found case for a VIN with no live listing is disclosed as well.

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?