Irish Used Car Market Data

Used-car prices by Irish county

prices_by_county

Read-onlyIdempotent

Use to see where a model (or make, or all cars) is cheapest or dearest across Irish counties, relative to the national median. Small counties may have few listings. Use market_stats instead when county comparison is not needed. Costs 0.01 USDC per call via x402; no-data results are free.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`make`	No	Optional make filter.	Toyota
`model`	No	Optional model filter (use with make).	Corolla

Output Schema

TableJSON Schema

Name	Required	Description	Default
`counties`	Yes
`national_median_price_eur`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 15, 2026

addedOutput schema / properties / counties / items / required

Added value: +[
+  "county",
+  "count",
+  "median_price_eur",
+  "vs_national_median_pct"
+]

addedOutput schema / required

Added value: +[
+  "national_median_price_eur",
+  "counties"
+]

Changed9 schema fields changedOct 15, 2026

addedInput schema / properties / make / default
```
Added value: +"Toyota"
```
addedInput schema / properties / make / example
```
Added value: +"Toyota"
```
addedInput schema / properties / make / examples
```
Added value: +[
+  "Toyota"
+]
```
addedInput schema / properties / model / default
```
Added value: +"Corolla"
```
addedInput schema / properties / model / example
```
Added value: +"Corolla"
```
addedInput schema / properties / model / examples
```
Added value: +[
+  "Corolla"
+]
```

addedOutput schema / properties / counties / items

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "county": {
+      "type": "string"
+    },
+    "median_price_eur": {
+      "type": "number"
+    },
+    "vs_national_median_pct": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / counties / type
```
Added value: +"array"
```
addedOutput schema / properties / national_median_price_eur / type
```
Added value: +"number"
```

First observedOct 15, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), so the description correctly spends its words elsewhere: per-call cost of 0.01 USDC via x402, free no-data results, and a data-quality caveat that small counties may have few listings. It stops short of describing pagination or result-size behavior, so not a 5.

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 dense sentences: purpose first, routing alternative second, operational caveats last. No filler and nothing buried mid-paragraph.

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 cost, data-sparsity caveat, and sibling routing all covered alongside annotations that carry the safety profile, an agent has everything needed to call this correctly.

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, but the description adds real meaning the schema obscures: it explains that a model, a make, or no filter at all are all valid queries ('or all cars'), which counteracts the schema's misleading Toyota/Corolla defaults, and it notes model should be paired with make.

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 analytical verb and resource: where a model/make/all cars is cheapest or dearest across Irish counties, normalized against the national median. That scope is distinct from sibling market_stats, so an agent can route 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 use case and names the exclusion explicitly: 'Use market_stats instead when county comparison is not needed.' The when-to-use condition and the named alternative are both present.

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?