Skip to main content
Glama
Sign In

Cro Ireland

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ie Get Company

ie_get_company
Read-onlyIdempotent

One Irish company by its CRO number (the Companies Registration Office's statutory register number), from the CRO's own Company Records open data. Returns current registered name, status, company type, registered address, eircode, incorporation date, last/next annual-return dates, last accounts date and dissolution date when applicable. Use ie_search_companies first if you only have a name.

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": {
      "cro_number": "249885"
    },
    "name": "ie_get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
cro_numberYesCRO company number, e.g. "249885" (Ryanair Holdings plc).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so safety is covered. The description adds genuine context beyond them: the upstream source is CRO open data, and it enumerates the returned fields (name, status, type, address, eircode, dates), which matters because no output schema exists. It stops short of noting rate limits, auth requirements, or freshness/lag of the register.

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?

Three sentences, front-loaded with the core operation, then the return payload, then the routing hint. The field enumeration is dense but justified since there is no output schema; no sentence is 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 carries the return-value burden and does so by listing the returned attributes and noting dissolution date is conditional. It also covers the input identifier semantics and the alternative path, so an agent has everything needed to call it correctly.

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% and the schema already supplies an example value, so baseline is 3. The description earns an extra point by defining what the CRO number actually is (the statutory register number issued by the Companies Registration Office), which prevents confusion with VAT or other company identifiers.

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 and resource ('One Irish company by its CRO number') and precisely disambiguates the identifier as the Companies Registration Office's statutory register number, plus names the data source (CRO Company Records open data). An agent can distinguish this from ie_search_companies and company_register_search at a glance.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Use ie_search_companies first if you only have a name.' This is a clear precondition that selects between the two sibling lookup tools, leaving nothing to inference.

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