Skip to main content
Glama

Catalogue of Irish data sources

ireland_catalogue
Read-onlyIdempotent

List sources and their operations, grouped by domain: stats, transport, environment, energy, economy, law/politics, places/property. Start here. Filter by topic, geo_level (national, nuts2, nuts3, county, local_authority, constituency, lea, ed, small_area, town, point), join_key, has_time_series or text to get matching operations with compact dataset cards (geography, time coverage, cadence, join keys).

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_catalogue"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoWords that must all appear in the source, operation or card.
topicNoTopic, e.g. housing, population, labour, transport, law. Related topics also match.
domainNoOnly this domain.
join_keyNoKey the results expose for joining, e.g. county_name, lea_name, ed_code, member_code, eli, lat_lon.
geo_levelNoGeography level the data is broken down by, e.g. county, local_authority, lea, ed, small_area, constituency, point.
has_time_seriesNotrue: data over several periods; false: current or single-period data.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / geo_level
      Added value: +{
      +  "description": "Geography level the data is broken down by, e.g. county, local_authority, lea, ed, small_area, constituency, point.",
      +  "maxLength": 40,
      +  "type": "string"
      +}
    • addedInput schema / properties / has_time_series
      Added value: +{
      +  "description": "true: data over several periods; false: current or single-period data.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / join_key
      Added value: +{
      +  "description": "Key the results expose for joining, e.g. county_name, lea_name, ed_code, member_code, eli, lat_lon.",
      +  "maxLength": 40,
      +  "type": "string"
      +}
    • addedInput schema / properties / text
      Added value: +{
      +  "description": "Words that must all appear in the source, operation or card.",
      +  "maxLength": 100,
      +  "type": "string"
      +}
    • addedInput schema / properties / topic
      Added value: +{
      +  "description": "Topic, e.g. housing, population, labour, transport, law. Related topics also match.",
      +  "maxLength": 40,
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / additionalProperties
      Previous value: -{}New value: +true
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, open-world behavior. The description adds useful result-shape context by saying matches return compact dataset cards with geography, time coverage, cadence, and join keys, though it does not mention ordering or pagination behavior.

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?

The description is compact and front-loaded: it first states what the tool lists, then says to start here, then summarizes filtering and return-card contents. Every sentence contributes 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?

Given the rich schema, full parameter coverage, output schema, and annotations, the description is largely complete for a catalogue entry-point tool. It could still do more to route agents explicitly among sibling tools, but no critical invocation information is missing.

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%, so the schema already documents all six filters and their meanings. The description contextualizes them as filters for matching operations and cards, but adds little parameter-level detail beyond what the schema already provides.

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 uses a specific verb and resource ('List sources and their operations') and states the domain grouping. 'Start here' also helps distinguish this catalogue/entry-point tool from action-oriented siblings such as fetch, call, or describe.

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

Usage Guidelines4/5

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

It clearly signals when to use it with 'Start here' and explains the available filtering dimensions. However, it does not explicitly name alternatives or state when not to use it versus siblings like search or ireland_describe.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.