Irish Used Car Market Data

Newly listed below-market cars since a given time

get_new_deals

Read-onlyIdempotent

Use to poll for fresh opportunities: returns deals first seen by us since a timestamp (default: last 24 hours). Call on a schedule with the previous call's time to receive only new deals. Use get_irish_auto_arbitrage_feed instead for the current ranked deal list regardless of first-seen time, or get_price_drops for discount signals. Costs 0.02 USDC per call via x402; no-data results are free.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`make`	No	Only this make.	Volkswagen
`limit`	No	Maximum results, 1-500.
`since`	No	ISO 8601 timestamp. Defaults to 24 hours ago.	2026-10-14T08:00:00Z
`min_margin_eur`	No	Minimum margin in EUR.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`since`	Yes
`listings`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 15, 2026

addedOutput schema / properties / listings / items / required

Added value: +[
+  "source_platform",
+  "listing_id",
+  "make",
+  "model",
+  "year",
+  "price_eur",
+  "mileage_km",
+  "fuel_type",
+  "transmission",
+  "county"
+]

addedOutput schema / required

Added value: +[
+  "since",
+  "count",
+  "listings"
+]

Changed16 schema fields changedOct 15, 2026

addedInput schema / properties / limit / default
```
Added value: +20
```
addedInput schema / properties / limit / example
```
Added value: +20
```
addedInput schema / properties / limit / examples
```
Added value: +[
+  20
+]
```
addedInput schema / properties / make / default
```
Added value: +"Volkswagen"
```
addedInput schema / properties / make / example
```
Added value: +"Volkswagen"
```
addedInput schema / properties / make / examples
```
Added value: +[
+  "Volkswagen"
+]
```
addedInput schema / properties / min_margin_eur / default
```
Added value: +1500
```
addedInput schema / properties / min_margin_eur / example
```
Added value: +1500
```
addedInput schema / properties / min_margin_eur / examples
```
Added value: +[
+  1500
+]
```
addedInput schema / properties / since / default
```
Added value: +"2026-10-14T08:00:00Z"
```
addedInput schema / properties / since / example
```
Added value: +"2026-10-14T08:00:00Z"
```
addedInput schema / properties / since / examples
```
Added value: +[
+  "2026-10-14T08:00:00Z"
+]
```
addedOutput schema / properties / count / type
```
Added value: +"integer"
```

addedOutput schema / properties / listings / items

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "county": {
+      "type": "string"
+    },
+    "fuel_type": {
+      "type": "string"
+    },
+    "listing_id": {
+      "type": "string"
+    },
+    "make": {
+      "type": "string"
+    },
+    "mileage_km": {
+      "type": "integer"
+    },
+    "model": {
+      "type": "string"
+    },
+    "price_eur": {
+      "type": "number"
+    },
+    "source_platform": {
+      "type": "string"
+    },
+    "transmission": {
+      "type": "string"
+    },
+    "year": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / listings / type
```
Added value: +"array"
```
addedOutput schema / properties / since / type
```
Added value: +"string"
```

First observedOct 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent/no-destruction, and the description adds traits they do not: per-call cost (0.02 USDC via x402), a free no-data outcome, and incremental polling semantics. That is exactly the value-add expected when annotations exist.

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 front-loaded sentences with no filler: purpose, operating pattern, alternatives, then cost. Every sentence carries distinct information an agent needs.

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 values need not be explained, and the description still covers defaults, polling mechanics, pricing, and routing to siblings. Nothing needed to 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%, so the baseline is 3; the description goes slightly beyond by explaining how to drive `since` incrementally (pass the previous call's time) and restating the 24-hour default window. It does not explain make/limit/min_margin_eur beyond what the schema documents.

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 and resource with scope: 'returns deals first seen by us since a timestamp (default: last 24 hours).' This clearly distinguishes it from the ranked feed and price-drop siblings without requiring a schema read.

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 explicit when-to-use ('poll for fresh opportunities'), an operating pattern ('call on a schedule with the previous call's time'), and names two alternatives with the conditions that select them (get_irish_auto_arbitrage_feed for current ranked lists, get_price_drops for discount signals).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Irish Used Car Market Data 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?