Ireland MCP

Resolve an Irish place to every geography code

ireland_resolve_place

Read-onlyIdempotent

All geography codes for an Irish place: county, province, council, LEA, Dáil constituency, NUTS3, electoral division (ED) and, for lat/lon, small area, with population shares where areas straddle. Takes a name (English or Irish, 'Co. Mayo', 'Dublin 8', 'Tallaght Central, South Dublin'), an ED/small-area/NUTS3 code, or lat/lon. list returns the EDs, LEAs, constituencies or councils inside.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ireland_resolve_place"
  }
}

Input Schema

Name	Required	Description
`lat`	No
`lon`	No
`list`	No	List areas of this level inside the place.
`level`	No	Only match this level.
`limit`	No
`place`	No	Name or code, e.g. 'Ballymun', 'Galway West', 'IE042', '268015'.
`offset`	No
`max_tokens`	No	Result budget in tokens (default 2000).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds meaningful context beyond that: lat/lon resolves to small area, straddling areas include population shares, and list returns contained areas.

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 front-load output scope, input forms, and list behavior with no filler. The phrasing is terse but every clause carries useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema and annotations present, the description covers the main resolution modes and output geography types. However, it omits the full list enum breadth and does not explain level or pagination semantics, leaving some complexity to the schema.

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 50%, and the description clarifies the critical place parameter accepts English/Irish names, codes, and examples, plus how lat/lon and list behave. It leaves level, limit, and offset to the schema, so it is helpful but not fully complete.

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?

The description names the specific resource and enumerates the geography code types returned, while also stating accepted input forms. This clearly distinguishes it from generic siblings like fetch, search, or nearby.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains accepted input forms and the list mode, implying when to use the tool, but it does not explicitly state when to prefer nearby/search or any exclusions, prerequisites, or ambiguity-handling guidance.

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

All Ireland MCP 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.