Skip to main content
Glama
Sign In

Cro Ireland

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ie Search Companies

ie_search_companies
Read-onlyIdempotent

Search Ireland's company register (CRO -- the Companies Registration Office) by the start of a company's current registered name. Returns each match's CRO number, name, status (e.g. Normal/Dissolved/Liquidation), type, registered address and incorporation date. Prefix match only ("Ryanair" finds "RYANAIR DESIGNATED ACTIVITY COMPANY" and "RYANAIR HOLDINGS PUBLIC LIMITED COMPANY" but not "Jet2Ryanair"); case/punctuation-insensitive. The CRO registers the SAME legal entity under slightly different name spellings over time (suffix "LIMITED" vs "LTD", "DESIGNATED ACTIVITY COMPANY" vs "DAC") -- try both forms if a name search comes back thin. Use the returned cro_number with ie_get_company for full detail or ie_get_filings for its filing history.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
nameYesStart of the company's current registered name, e.g. "Ryanair".
limitNoMaximum results (1-100, default 20).
statusNoFilter to one of the register's own status TEXT values, e.g. "Normal" or "Dissolved" (case-sensitive, as the CRO publishes it). Omit to search across every status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, so the description is free to add the traits that matter: prefix-only matching, case/punctuation insensitivity, and the same-entity/different-spelling pitfall. The enumerated return fields also tell the agent what it will get without an output schema.

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?

Front-loads the purpose and match semantics first, then the returned fields, then the retry heuristic and the hand-off to detail tools. Every sentence carries actionable information with no filler.

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?

With no output schema, the description supplies the return fields (CRO number, name, status, type, address, incorporation date), an example of status values, and the follow-up call pattern. An agent has everything needed to invoke it and act on the result.

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, but the description adds real meaning: it clarifies that 'name' is a prefix of the current registered name (not a substring or fuzzy match) and that matching is case/punctuation-insensitive, which the schema's brief field notes don't fully convey.

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?

Names a specific verb (Search) and a precise resource (Ireland's company register, CRO), and states the exact matching rule (start of current registered name). The prefix-only behavior clearly separates it from a general/fuzzy register search and from the ie_get_company/ie_get_filings detail siblings.

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?

Gives explicit routing: 'Use the returned cro_number with ie_get_company for full detail or ie_get_filings for its filing history,' plus a practical retry rule when results are thin (try LIMITED vs LTD, DAC vs DESIGNATED ACTIVITY COMPANY). It doesn't explicitly contrast with the sibling company_register_search, so it stops short of full when-not guidance.

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

All Cro Ireland toolsInspect
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.

Resources