Skip to main content
Glama

regdata_ireland_cro

Look up Irish companies in the official CRO register by name or CRO number to get identity, status, incorporation date, address, and email. A verified not-found is a real answer.

Instructions

Ireland CRO Company Registry Scraper. Look up Irish companies in the official CRO register by name or CRO number. Returns identity, type, status, incorporation date, registered address and email. Directors/shareholders are paid CRO documents and not included. A verified "not found" is a real answer. Advanced fields beyond this schema are also accepted (regdata_describe lists them).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxItemsNoOptional cap on billed dataset items returned.
companyNamesNoOne or more company names to search, each looked up separately (min 2 characters). Partial names work. A broad name can hit the register's 50-result ceiling.
statusFilterNoKeep only companies whose status contains one of these words, e.g. 'Normal', 'Dissolved', 'Liquidation'. Leave empty to export every match - a Dissolved or Liquidation counterparty is usually the finding you most want to see.
companyNumbersNoOne or more Irish CRO registration numbers, each looked up separately. Digits only, e.g. '104547'.
maxResultsPerQueryNoMaximum company records to export per query. The register returns at most 50 matches per search, so 50 is the ceiling. Fetching the full record for each match happens in the same run.
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that directors/shareholders are not included (paid documents) and that 'not found' is an answer. It lacks details on rate limits or auth, but for a registry scraper this is adequate.

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 concise with no redundant information. It front-loads the purpose and covers key details in two sentences plus a few clarifications. Every sentence adds value.

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?

Given no output schema, the description fully explains what is returned (identity, type, status, date, address, email) and what is not (directors/shareholders). It also notes advanced fields via regdata_describe. Complete for a registry lookup.

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 coverage is 100%, so baseline is 3. The description adds context like 'A broad name can hit the register's 50-result ceiling' but does not significantly go beyond schema descriptions. Adequate.

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 clearly states it is an 'Ireland CRO Company Registry Scraper' that looks up Irish companies by name or CRO number, and lists return fields. It distinguishes from sibling tools by specifying the Irish CRO register, which is unique among the 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?

The description provides guidance on advanced fields via regdata_describe and clarifies that 'not found' is a valid answer. However, it does not explicitly compare with sibling tools or state when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nolpak14/getregdata'

If you have feedback or need assistance with the MCP directory API, please join our Discord server