Skip to main content
Glama
Sign In

UK Companies House due diligence and KYB (Registrum)

by io.github.RegistrumUK
OverviewDiscussionsAdmin

Get company financials

get_financials
Read-onlyIdempotent

Get structured financial data for a UK company, parsed from its iXBRL accounts filed at Companies House. Returns revenue, cost of sales, gross profit, operating profit, net profit, fixed assets, current assets, total equity, net assets, creditors, and average employees for the current and prior reporting year. Also includes accounts_type (full, abbreviated, micro, dormant or unknown) and a data_quality block indicating which fields were extracted and which were absent. period_end is the end of the accounting period the figures cover (the year the accounts end), NOT the date the accounts were filed; the filing date is data_quality.filed_on. Other data_quality fields: filing_type (Companies House form code: AA, AAMD or AC(NI)), period_end_source and accounts_type_source (how those two values were determined), and accounts_description_code (the verbatim Companies House code, e.g. unaudited-abridged, micro-entity). Unaudited-abridged, small and audit-exemption-subsidiary filings are abbreviated, not full, and carry no profit and loss (check has_profit_loss). accounts_type is unknown when it could not be determined; do not assume full. The response can be available: false with an unavailable_reason: image_pdf (accounts filed as a scanned PDF, common for large companies such as Tesco), no_ixbrl_filings (no digital filing), or dissolved. That means no figures could be extracted; it does not mean the company has no accounts. Cached for 7 days.

Input Schema

NameRequiredDescriptionDefault
company_numberYesCompanies House company number, e.g. '00445790' for Tesco PLC. Numeric-only numbers should be zero-padded to 8 digits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: a 7-day cache, the available:false path with three distinct unavailable_reason values (image_pdf, no_ixbrl_filings, dissolved), and the crucial clarification that unavailable does NOT mean the company has no accounts. It also warns that abbreviated filings carry no profit and loss.

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?

Front-loaded with the core purpose and returned fields, then moves to caveats. It is a dense, long paragraph, but nearly every sentence carries non-obvious semantics (period_end vs filed_on, accounts_type unknown, abbreviated filings). Slightly heavy but well organized.

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?

There is no output schema, so the description carries the full burden of explaining the return shape — it does so exhaustively via the field list, data_quality block and the available:false structure. An agent has everything needed to interpret a response.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents the format, example and zero-padding rule. The description adds nothing about company_number, so the baseline 3 applies.

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 ('Get structured financial data for a UK company') plus the exact source ('parsed from its iXBRL accounts filed at Companies House'). Enumerates the returned fields, which clearly separates it from siblings like get_company, get_directors and get_compliance.

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?

The description implies usage strongly through its content (what the data is, when the response is unavailable) but never explicitly states when to choose this over get_company or other siblings. It explains data-availability edge cases rather than routing guidance, so usage remains inferred rather than directed.

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

All UK Companies House due diligence and KYB (Registrum) 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