OmniaAuto — Canadian Vehicle Listings

decode_vin

Read-onlyIdempotent

COST: free (uses no OmniaAuto credits).

Decode a VIN into full specs: year, make, model, trim, body, drivetrain, engine and more. Works for any VIN, listed for sale or not; use get_vin for its live listing, price and listing_url. A malformed VIN returns error invalid_vin.

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
`vin`	No
`make`	No
`note`	No
`trim`	No
`year`	No
`error`	No	Set on a refusal, e.g. out_of_credits, not_found; result fields are then absent
`model`	No
`decode_ok`	No	False when the VIN could not be decoded
`body_class`	No
`drive_type`	No
`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": {
+    "body_class": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "credits_remaining": {
+      "description": "Credits left in the current period",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "decode_ok": {
+      "description": "False when the VIN could not be decoded",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "drive_type": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "error": {
+      "description": "Set on a refusal, e.g. out_of_credits, not_found; result fields are then absent",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "make": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "model": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "trim": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "vin": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "year": {
+      "type": [
+        "integer",
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds non-obvious behavior: it consumes no OmniaAuto credits and returns a specific error code 'invalid_vin' for malformed input. It stops short of describing the response shape, but with an output schema present that is acceptable.

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 compact sentences: cost first, then capability, then routing and error behavior. Every sentence earns its place and the most decision-relevant fact (free) is front-loaded.

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 single-parameter read tool with annotations and an output schema, the description covers cost, scope, sibling routing, and the error contract. Nothing an agent needs to select or invoke 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% and the vin property already documents the 17-character rule, allowed characters, and case-insensitivity. The description adds the failure mode (invalid_vin) tied to that parameter, which is a small but real increment over the schema.

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 specific verb (decode) and resource (VIN) and enumerates the returned specs (year, make, model, trim, body, drivetrain, engine). It also names the sibling get_vin and how it differs, so an agent can distinguish the two without opening schemas.

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?

Explicitly says it works for any VIN 'listed for sale or not' and directs the agent to get_vin when live listing, price, and listing_url are wanted. Both the use case and the alternative are named, leaving nothing to inference.

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?