Ireland MCP

Call an operation

ireland_call

Read-onlyIdempotent

Run a source operation with args. Bad args return the expected schema and an example. Operations by source: cso: cso_search_tables, cso_get_table_metadata, cso_get_data, cso_area_profile; lobbying: lobbying_search_returns; paygap: paygap_search_reports; council-budgets: council_budgets_list_years, council_budgets_get; ncse: ncse_search_datasets, ncse_get_dataset, ncse_query_datastore; world-bank: worldbank_get_indicator, worldbank_ireland_profile; eurostat: eurostat_search_datasets, eurostat_get_data, eurostat_compare_ie_eu; ecb: ecb_get_series, ecb_interest_rates, ecb_exchange_rate; pobal: pobal_deprivation_search; oireachtas: oireachtas_search_members, oireachtas_search_bills, oireachtas_get_bill, oireachtas_get_debates, oireachtas_search_questions, oireachtas_get_votes; geohive: geohive_boundaries_at_point, geohive_locate, geohive_list_layers, geohive_query_layer; wikidata: wikidata_place, wikidata_entity; data-gov-ie: datagov_search_datasets, datagov_get_dataset, datagov_query_datastore; cro: cro_search_datasets, cro_get_dataset, cro_query_datastore; kohesio: kohesio_search_projects, kohesio_get_project; smart-dublin: smartdublin_search_datasets, smartdublin_get_dataset, smartdublin_query_datastore; met-eireann: met_get_forecast, met_get_observations, met_get_warnings; nta: nta_get_realtime_summary, nta_get_trip_updates; legislation: legislation_list_acts, legislation_get_act, legislation_get_section, legislation_get_act_effects, legislation_list_sis, legislation_get_si, legislation_get_constitution_article; eu-law: eu_law_lookup; ppr: ppr_search_sales, ppr_price_stats; irish-rail: rail_find_station, rail_get_departures; luas: luas_get_forecast, luas_list_stops; eirgrid: grid_get_status; marine: marine_get_buoys; opw-water: water_find_stations, water_get_level; planning: planning_search, planning_get; census-areas: census_small_area_at; epa: epa_wfd_search, epa_wfd_waterbody, epa_bathing_locations, epa_bathing_alerts, epa_bathing_measurements; heritage: heritage_monuments_near; environment-sites: protected_sites_at, protected_sites_near; ted: ted_search_tenders, ted_get_notice; bikes: bikes_networks, bikes_stations_near; failte-ireland: failte_search; tfi-static: tfi_static_search_stops; gsi: groundwater_vulnerability_at; logainm: logainm_search_places; cib: cib_cis_annual_summary, cib_cis_query_categories, cib_cips_summary; civic-directory: civic_directory_search; cross: list_sources, ireland_snapshot, nearby, ireland_resolve_place.

Input Schema

Name	Required	Description
`args`	No	Operation arguments.
`source`	Yes	Source id.
`arguments`	No	Alias of args.
`operation`	Yes	Operation name.
`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.

Changed1 schema field changedOct 7, 2026

addedInput schema / properties / arguments

Added value: +{
+  "additionalProperties": true,
+  "description": "Alias of args.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

Changed2 schema fields changedOct 7, 2026
- changedInput schema / properties / args / additionalProperties
```
Previous value: -{}New value: +true
```
- changedOutput schema / additionalProperties
```
Previous value: -{}New value: +true
```
First observedOct 6, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds useful context that bad arguments return the expected schema and an example, plus the full supported-source coverage, but it does not explain dispatch semantics such as unknown source/operation handling, auth requirements, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is front-loaded and every operation name plausibly earns its place as a selection aid. However, the catalogue is a dense, unstructured wall of text rather than a scannable grouping, which hurts readability for such a large dispatcher.

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?

An output schema exists, annotations cover the safety profile, and all five parameters are described in the schema. The description adds the full operation catalogue and error-recovery behavior, making it largely complete for invocation; only routing mechanics and per-operation argument expectations are left implicit via the bad-args fallback.

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. The description goes beyond the schema by enumerating the valid source-to-operation mapping, which functions as an enum-like selection guide not present in the input schema, materially helping the agent populate source and operation correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Run') and resource ('source operation with args'), and the source-to-operation catalogue makes the dispatcher role concrete. It does not explicitly contrast itself with siblings like ireland_describe or ireland_catalogue, so it stops short of a 5.

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?

The operation catalogue implicitly tells the agent which source/operation pair to pick, and 'Bad args return the expected schema and an example' gives error-recovery guidance. However, there is no explicit statement of when to use this tool versus ireland_describe, ireland_catalogue, search, or fetch, and no exclusions.

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.