Skip to main content
Glama
Sign In

Cro Ireland

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ie Get Filings

ie_get_filings
Read-onlyIdempotent

An Irish company's filing/submission history (annual returns, accounts, charges, etc.) by CRO number, from the CRO's (Companies Registration Office) own live Open Services API. This data is not in the CRO's open-data snapshot, only in its live, access-controlled API; Pipeworx supplies a CRO Open Services credential, so no key is needed. Optional: use your own CRO Open Services account by passing your registered email as _apiKey and the API key as _apiSecret (or both as _apiKey "email:key"). Use company_bus_ind 'B' for a registered business name rather than a company.

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_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
_apiKeyNoOptional: your own CRO Open Services account email (or "email:key"). Pipeworx supplies one if omitted.
_apiSecretNoOptional: the CRO Open Services API key issued to that account.
cro_numberYesCRO company number, e.g. "249885".
company_bus_indNo'C' for a company (default), 'B' for a registered business name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"CRO Open Services account email (the CustomerKey login)."New value: +"Optional: your own CRO Open Services account email (or \"email:key\"). Pipeworx supplies one if omitted."
    • changedInput schema / properties / _apiSecret / description
      Previous value: -"CRO Open Services API key issued to that account."New value: +"Optional: the CRO Open Services API key issued to that account."
    • addedInput schema / properties / company_bus_ind
      Added value: +{
+  "description": "'C' for a company (default), 'B' for a registered business name.",
+  "enum": [
+    "C",
+    "B"
+  ],
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "cro_number",
-  "_apiKey",
-  "_apiSecret"
-]New value: +[
+  "cro_number"
+]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior. The description adds genuinely useful context beyond that: the data exists only in the live access-controlled CRO API, not the open-data snapshot, and Pipeworx supplies a credential so no key is required, with an option to pass your own. It stops short of describing the response shape or what happens on an unknown CRO number.

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?

Two sentences are front-loaded with the purpose before the credential and business-name notes. It is dense but each sentence carries distinct information, with only minor redundancy between the description and the schema on the _apiKey formats.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only lookup with no output schema, the description gives the entity scope, the data source, the credential model, and the filing types returned. It could go further by sketching the returned record structure or pagination behavior, but an agent has enough to invoke it correctly.

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 every parameter including the _apiKey/_apiSecret credential pair and the company_bus_ind enum is already documented. The description restates these and adds the minor convenience of passing 'email:key' as a single _apiKey, which is a small increment over the schema baseline.

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 (retrieve) and resource (an Irish company's filing/submission history: annual returns, accounts, charges) keyed by CRO number, and names the data source (CRO Open Services live API). An agent can distinguish this from ie_get_company and ie_search_companies by the fact that it returns filings rather than company details or search results.

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

Usage Guidelines3/5

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

Usage context is implied (this is the tool for filing history of an Irish entity), and it explains the 'B' value for registered business names versus companies. However, it never says when to choose this over sibling tools like ie_get_company, nor does it state prerequisites such as needing a valid CRO number existing in the register.

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