OmniaAuto — Canadian Vehicle Listings

My Usage

my_usage

Read-onlyIdempotent

COST: free (no credits).

Returns the account's OmniaAuto plan, credits used and remaining, reset date and per-tool credit costs.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`note`	No
`plan`	No
`error`	No	Set on a refusal, e.g. out_of_credits, not_found; result fields are then absent
`plans_url`	No
`resets_on`	No	Date credits reset, YYYY-MM-DD; null when they do not refill
`plan_label`	No
`tool_costs`	No	Credits per call, by tool
`credits_used`	No
`rows_per_search`	No	Maximum vehicles per search_listings call
`credits_included`	No	Credits in the current period; null on an account with no limit
`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": {
+    "credits_included": {
+      "description": "Credits in the current period; null on an account with no limit",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "credits_remaining": {
+      "description": "Credits left in the current period",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "credits_used": {
+      "type": [
+        "integer",
+        "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"
+      ]
+    },
+    "plan": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "plan_label": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "plans_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "resets_on": {
+      "description": "Date credits reset, YYYY-MM-DD; null when they do not refill",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "rows_per_search": {
+      "description": "Maximum vehicles per search_listings call",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "tool_costs": {
+      "additionalProperties": {
+        "type": "integer"
+      },
+      "description": "Credits per call, by tool",
+      "type": [
+        "object",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is low. The description adds genuinely useful context they do not: the operation is free and consumes no credits, plus what data categories come back (plan, credits used/remaining, reset date, per-tool costs).

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 with no filler; the cost constraint is front-loaded before the description of the returned data, which is the right ordering for an agent deciding whether to call it.

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 structure need not be spelled out, and the description still summarizes it. The only minor gap is that it never states the authentication/account-binding requirement implied by 'the account's plan', which an agent should know before calling.

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 the baseline is 4 and the description has nothing to document. It adds no parameter detail, but none is 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?

Names a specific resource and verb: returns the account's OmniaAuto plan, credits used/remaining, reset date, and per-tool credit costs. No sibling (coverage, decode_vin, get_vin, market_stats, search_listings, valuation) touches account/usage data, so an agent can distinguish it at a glance.

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?

There is no explicit when-to-use statement or named alternative, but the leading 'COST: free (no credits)' line gives practical guidance that this call is cheap and safe to invoke. That is implied usage context rather than real routing guidance.

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?