Skip to main content
Glama

Search Irish public data

search
Read-onlyIdempotent

Search across Central Statistics Office (CSO) PxStat, National Council for Special Education open data, World Bank Indicators for Ireland, Eurostat Statistics API, Pobal HP Deprivation Index, Houses of the Oireachtas Open Data API, Wikidata Query Service, data.gov.ie (Ireland's open data portal), Companies Registration Office open data, Kohesio EU-funded projects, Smart Dublin open data (Dublin local authorities), Irish Statute Book (eISB) via ELI, EPA Ireland open data, EU Tenders Electronic Daily (TED), Éire Civic Tech Directory (CitizenData.ie). Returns ids like 'cso:F1001' to pass to fetch.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look for, e.g. 'population by county' or 'housing bill 2024'.
max_tokensNoResult budget in tokens (default 2000).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / additionalProperties
      Previous value: -{}New value: +true
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld and idempotent, so the safety profile is covered. The description adds the return shape (prefixed ids like 'cso:F1001'), which is useful, but says nothing about ranking, result volume, or what an empty result looks like. With annotations carrying the behavioral load, a 3 is appropriate.

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

Conciseness4/5

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

The scope list is front-loaded and every source name earns its place by telling the agent what is searchable. It is long but single-purpose, with no filler; only mild redundancy across the many portal names keeps it from a 5.

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 not be spelled out, and the description still adds the crucial id-format hint needed to chain into fetch. For a two-parameter read-only search tool, nothing an agent needs before calling it 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 both the query string and max_tokens budget are already documented in the schema. The description contributes no additional parameter guidance (no query syntax, no advice on setting max_tokens), so the baseline 3 applies.

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 (Search) plus the exact resources covered, enumerating fifteen named Irish data sources so the agent knows the corpus scope. The closing sentence ('Returns ids like cso:F1001 to pass to fetch') distinguishes it cleanly from the sibling fetch tool.

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?

The description establishes an explicit two-step workflow by telling the agent the output is an id meant for fetch, which is genuine routing guidance. It does not say when to prefer this over siblings such as ireland_catalogue or ireland_describe, so the guidance is clear but incomplete.

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.