OmniaAuto — Canadian Vehicle Listings

my_usage

Read-onlyIdempotent

COST: free (uses no OmniaAuto credits).

Your OmniaAuto plan, credits used and remaining, reset date and per-tool costs. Use it to check the balance or after an out_of_credits error; it returns no vehicle data (use search_listings or market_stats). Works even with zero credits left.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON 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.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral facts not in structured data: the call is free, consumes no OmniaAuto credits, and still works at zero balance — important for an agent deciding whether it can call it after an out_of_credits failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Front-loaded cost line, then return contents, then usage guidance — efficient ordering. Slight redundancy across 'free', 'uses no OmniaAuto credits' and 'works even with zero credits left', which are three near-identical statements, costing a little density.

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 no-argument, read-only status tool with an output schema and full annotation coverage, the description supplies everything needed: what it returns, what it costs, when to call it, and what it does not return.

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; baseline 4 applies. No misleading parameter claims are made.

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 the specific resource returned — plan, credits used/remaining, reset date, per-tool costs — and explicitly excludes vehicle data, naming search_listings and market_stats as the tools for that. An agent can distinguish it from every sibling without opening a 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?

Gives two concrete triggers: checking the balance and recovering after an out_of_credits error, plus an explicit redirect to search_listings or market_stats when vehicle data is wanted. Both when-to-use and when-not-to-use are covered.

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?