Irish Used Car Market Data

How many used cars are listed in Ireland

get_inventory_summary

Read-onlyIdempotent

Returns one number: the count of active used-car listings in Ireland, with a timestamp. No breakdowns and no prices. Use get_inventory_breakdown instead for county, make, turnover and freshness details. Costs 0.005 USDC per call via x402; no-data results are free.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`as_of`	Yes
`access_note`	Yes
`active_listings`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

addedOutput schema / required

Added value: +[
+  "as_of",
+  "active_listings",
+  "access_note"
+]

Changed3 schema fields changedOct 15, 2026
- addedOutput schema / properties / access_note / type
```
Added value: +"string"
```
- addedOutput schema / properties / active_listings / type
```
Added value: +"integer"
```
- addedOutput schema / properties / as_of / 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 declare readOnly/idempotent/non-destructive, and the description goes further with details annotations cannot carry: the 'one number plus timestamp' return shape, the metered cost of 0.005 USDC per call via x402, and the fact that no-data results are free. Cost and output shape are exactly the behavioral context an agent needs here.

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, each earning its place: return shape first, exclusions and the alternative second, pricing last. No repetition of the title or schema content.

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 zero-parameter read tool with an output schema already present, the description covers everything an agent needs: scope, return shape, the alternative for detail, and the cost model. Nothing material 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?

The tool takes zero parameters (empty object schema, 100% coverage), so the baseline is 4. The description confirms there is nothing to filter by, reinforcing that no inputs are expected or accepted.

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 explicit scope: the count of active used-car listings in Ireland, plus a timestamp. It also names the sibling it is not (get_inventory_breakdown), so an agent can separate it from the 12 other tools 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?

Explicitly excludes what it does not do ('No breakdowns and no prices') and routes the agent to get_inventory_breakdown for county, make, turnover and freshness. The when-to-use condition and the alternative are both stated rather than 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?