irish-competition-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ie_comp_search_decisionsA | Full-text search across CCPC enforcement decisions (abuse of dominance, cartel, sector inquiries). Returns matching decisions with case number, parties, outcome, fine amount, and Competition Act articles cited. |
| ie_comp_get_decisionA | Get a specific CCPC decision by case number (e.g., 'B6-22/16', 'B2-94/12'). |
| ie_comp_search_mergersA | Search CCPC merger control decisions (Fusionskontrolle). Returns merger cases with acquiring party, target, sector, and outcome. |
| ie_comp_get_mergerA | Get a specific merger control decision by case number (e.g., 'B1-35/21', 'B8-101/18'). |
| ie_comp_list_sectorsA | List all sectors with CCPC enforcement activity, including decision counts and merger counts per sector. |
| ie_comp_aboutA | Return metadata about this MCP server: version, data source, coverage, and tool list. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct purpose: search vs. get for decisions and mergers, plus list_sectors and about. There is no overlap or ambiguity between tools.
All tools share the 'ie_comp_' prefix and follow a clear verb_noun pattern (search_decisions, get_decision, search_mergers, get_merger, list_sectors). The 'about' tool is a conventional exception for metadata, but the pattern remains highly consistent.
Six tools is well-scoped for a read-only competition law database. Each tool serves a necessary function without redundancy or bloat.
The tool set covers the full lifecycle for this domain: search and retrieve both decisions and mergers, browse sectors, and access server metadata. As a read-only API, no create/update/delete operations are expected, so there are no obvious gaps.