Irish Used Car Market Data

Irish used cars whose asking price was recently cut

get_price_drops

Read-onlyIdempotent

Use to find motivated sellers: listings whose price dropped within the last N days, with original, previous and current price and the percentage cut. Price history is recorded by us from the first time we see a listing. Use get_irish_auto_arbitrage_feed instead for below-market ranking even when there was no recent price cut. Costs 0.02 USDC per call via x402; no-data results are free.

Input Schema

TableJSON Schema

Name	Required	Description
`days`	No	Look-back window in days, 1-60.
`limit`	No	Maximum results, 1-500.
`min_drop_pct`	No	Minimum size of the latest cut, in percent.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	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",
+  "original_price_eur",
+  "previous_price_eur",
+  "current_price_eur",
+  "drop_eur",
+  "drop_pct",
+  "changed_at"
+]

addedOutput schema / required

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

Changed12 schema fields changedOct 15, 2026

addedInput schema / properties / days / default
```
Added value: +7
```
addedInput schema / properties / days / example
```
Added value: +7
```
addedInput schema / properties / days / examples
```
Added value: +[
+  7
+]
```
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 / min_drop_pct / default
```
Added value: +3
```
addedInput schema / properties / min_drop_pct / example
```
Added value: +3
```
addedInput schema / properties / min_drop_pct / examples
```
Added value: +[
+  3
+]
```
addedOutput schema / properties / count / type
```
Added value: +"integer"
```

addedOutput schema / properties / listings / items

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

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

First observedOct 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations cover the safety profile (read-only, idempotent, non-destructive, openWorld=false), and the description goes further in the ways that matter: it discloses the x402 paywall at 0.02 USDC per call, that no-data results are free, and the provenance limitation that price history only exists from our first observation of a listing. That last point materially affects interpretation of the days window and is not derivable from the schema.

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 sentences with no filler: purpose first, alternative second, cost/provenance third. Every sentence carries information an agent would otherwise have to guess.

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?

An output schema exists, so return values need no explanation. With zero required parameters, a 60-day cap on the window, cost, provenance limits and the sibling alternative all covered, nothing an agent needs in order to call this correctly is missing.

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?

Schema coverage is 100% and each parameter already carries a range and description, so the schema does the heavy lifting and a 3 is the correct baseline. The description adds only marginal meaning, notably that the 'drop' is the latest cut, which loosely frames min_drop_pct, and that the window is a look-back.

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 ('listings whose price dropped within the last N days') and enumerates the returned fields (original, previous, current price, percentage cut). It also names the sibling it is not (get_irish_auto_arbitrage_feed), so an agent can disambiguate without opening the 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 an explicit use case ('find motivated sellers') and an explicit alternative with the condition that selects it: get_irish_auto_arbitrage_feed for below-market ranking even when there was no recent price cut. It also discloses the cost model, which affects whether an agent should call it at all.

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?