OmniaAuto — Canadian Vehicle Listings

Get Vehicle by VIN

get_vin

Read-only

COST: 1 credit per call.

Returns the latest live listing for one VIN: price, mileage, location and listing_url.

Input Schema

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

Output 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

A3.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description adds a genuinely useful behavioral trait beyond the annotations: the 1-credit cost per call, and 'latest live' implies freshness-sensitive, time-varying results that explain the non-idempotent hint.

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 short sentences, cost front-loaded so the agent sees the billing implication first, then the return content. No filler or restated fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be enumerated; the description's listing of fields is mild redundancy but harmless. What an agent needs to call it is present, though sibling routing (decode_vin vs this) remains unresolved.

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?

Only one parameter, whose schema description is fully covered (100%) and already specifies the 17-character format and excluded letters. The description adds no syntax or format detail beyond 'one VIN', so the baseline 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?

States a specific verb and resource ('Returns the latest live listing for one VIN') and enumerates what comes back (price, mileage, location, listing_url). It is clearly distinct from a decode tool by virtue of returning 'live listing' data, but it never names a sibling to disambiguate from decode_vin or search_listings.

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

Usage Guidelines2/5

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

Discloses the cost (1 credit per call), which is useful context, but gives no when-to-use guidance: nothing tells the agent when to call get_vin instead of decode_vin or search_listings for VIN-based lookups, and no prerequisites or exclusions are stated.

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?