Irish Used Car Market Data

Irish used-car inventory by county and make, with turnover and freshness

get_inventory_breakdown

Read-onlyIdempotent

Use for market coverage and supply analysis: active used-car listings, optionally for one county and/or make, with a county and make breakdown, listings added in the last 24 hours, listings removed in the last 7 days, number of sources and when the data was last refreshed. Counts only; no prices. Use get_inventory_summary instead when you only need the one headline active-listing count. Costs 0.01 USDC per call via x402; no-data results are free.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`make`	No	Optional vehicle make, case-insensitive.	Toyota
`county`	No	Optional Irish county, e.g. Dublin, Cork, Galway (case-insensitive).	Dublin

Output Schema

TableJSON Schema

Name	Required	Description	Default
`as_of`	Yes
`filters`	Yes
`top_makes`	Yes
`history_days`	Yes
`source_count`	Yes
`added_last_24h`	Yes
`active_listings`	Yes
`removed_last_7d`	Yes
`last_data_refresh`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 15, 2026

addedOutput schema / properties / filters / required
```
Added value: +[
+  "county",
+  "make"
+]
```
addedOutput schema / properties / top_makes / items / required
```
Added value: +[
+  "make",
+  "count"
+]
```

addedOutput schema / required

Added value: +[
+  "as_of",
+  "filters",
+  "active_listings",
+  "source_count",
+  "history_days",
+  "added_last_24h",
+  "removed_last_7d",
+  "last_data_refresh",
+  "top_makes"
+]

Changed18 schema fields changedOct 15, 2026
- addedInput schema / properties / county / default
```
Added value: +"Dublin"
```
- addedInput schema / properties / county / example
```
Added value: +"Dublin"
```
- addedInput schema / properties / county / examples
```
Added value: +[
+  "Dublin"
+]
```
- addedInput schema / properties / make / default
```
Added value: +"Toyota"
```
- addedInput schema / properties / make / example
```
Added value: +"Toyota"
```
- addedInput schema / properties / make / examples
```
Added value: +[
+  "Toyota"
+]
```
- addedOutput schema / properties / active_listings / type
```
Added value: +"integer"
```
- addedOutput schema / properties / added_last_24h / type
```
Added value: +"integer"
```
- addedOutput schema / properties / as_of / type
```
Added value: +"string"
```
- addedOutput schema / properties / filters / additionalProperties
```
Added value: +true
```
- addedOutput schema / properties / filters / properties
```
Added value: +{
+  "county": {
+    "type": "string"
+  },
+  "make": {}
+}
```
- addedOutput schema / properties / filters / type
```
Added value: +"object"
```
- addedOutput schema / properties / history_days / type
```
Added value: +"number"
```
- addedOutput schema / properties / last_data_refresh / type
```
Added value: +"string"
```
- addedOutput schema / properties / removed_last_7d / type
```
Added value: +"integer"
```
- addedOutput schema / properties / source_count / type
```
Added value: +"integer"
```
- addedOutput schema / properties / top_makes / items
```
Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "make": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
```
- addedOutput schema / properties / top_makes / type
```
Added value: +"array"
```
First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds genuinely non-structured traits: a 0.01 USDC x402 cost per call, free no-data results, and that output is counts only with no prices. It does not cover error behavior or any rate limits beyond cost, so it stops just short of full transparency.

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-loads purpose and scope, then the alternative, then cost. Dense but every clause earns its place; the single long first sentence carries a lot of enumeration that could be trimmed slightly, which keeps it from a 5.

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-value detail is not needed. Between the description (content scope, cost, no-data behavior, alternative tool) and the annotations (safety profile), an agent has everything required to select and invoke it correctly.

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 description coverage is 100% and both parameters are documented there as optional, case-insensitive filters. The description restates that filtering by county and/or make is optional but adds no syntax, matching behavior, or default semantics beyond the schema, so the baseline of 3 applies.

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 ('active used-car listings') plus the exact scope of the payload: county/make breakdown, 24h additions, 7d removals, source count, last refresh. It explicitly names the sibling it is not (get_inventory_summary), so an agent can route between the two without opening either 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?

Opens with the intended use case ('market coverage and supply analysis') and gives an explicit when-not rule with the named alternative: use get_inventory_summary for a single headline count. Both the selection condition and the alternative are stated, not implied.

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?