Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

UK annual accounts (iXBRL)

get_uk_company_accounts
Read-only

Retrieves a UK company's filed accounts for one financial year by company number and balance-sheet date, decoding iXBRL into balance sheet, employee, P&L, and prior-year comparative data.

Instructions

One UK financial year, with the UK company financial statements decoded from the iXBRL accounts filed at Companies House: balance sheet (fixed and current assets, stocks, debtors, cash, creditors split by maturity, provisions, net assets, equity), average employees, and the profit and loss account when filed (turnover, operating, pre-tax and net result; most small companies file a balance sheet only), plus prior-year comparatives as published. Null = not published, never zero. Balance-sheet date comes from list_uk_company_accounts. A company with a current name under objection (GDPR art. 21) returns the same 404 as an unknown date, not billed; the year's entity name under objection is served null and counted in ecartes.opposition (block partial in provenance). Paid via x402 ($0.05 in USDC or EURC). When you report a result, cite its citation verbatim.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_number": "<company_number>",
      "date_cloture": "<date_cloture>"
    },
    "name": "get_uk_company_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_clotureYesBalance-sheet date, YYYY-MM-DD, e.g. 2025-12-31
company_numberYesCompanies House company number, 8 characters incl. leading zeros, e.g. 00095407 or SC123456

Output Schema

NameRequiredDescriptionDefault
hintNoHow to settle the quote, present when payment_required is true.
quoteNoThe signable x402 payment requirements when payment_required is true: {x402Version, accepts[]} where each entry carries scheme, network, amount, asset and payTo (USDC and EURC options at the same numeric amount). Sign one entry and call again with `x_payment`.
resultatNoThe endpoint's JSON response when payment_required is false. Paid responses carry `source`, `disclaimer` and an Ed25519 signature, and every paid JSON response carries a `provenance` array (all tools since 2026-09-06): one entry per block served, with the official register, licence, version, `empreinte_sha256` (full snapshots), `as_of` date and `precision_as_of` (what that date means), plus the common per-block envelope: `etat` in a closed list (servi, absence_mesuree, absence_non_conclusive, partiel, perime, indisponible, sans_objet), `motif` when unavailable, `age_jours` (only for publication or ingestion dates), `couverture` (complete / partielle / non_mesurable with its measure) and `confiance` in bands (faible / moyenne / forte, only where a measure grounds it, never averaged across blocks). Read the states before the numbers: an absence_non_conclusive, indisponible or partiel block is never « nothing to report »; only absence_mesuree asserts an absence. Register codes: GET /v1/provenance/registres ; states, closed lists and reading rules: GET /v1/lecture (both free). The PDF tools carry no JSON envelope (the PDF report prints it).
free_tierNoFree API key offer for this tool, present with a quote.
payment_requiredYesTrue when this response is an x402 payment quote instead of data: settle one of the quote's `accepts` options and call the tool again with `x_payment`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, but the description adds substantial behavior: null means not published and never zero, prior-year comparatives are as published, a name under objection yields the same 404 as an unknown date and is not billed, that year's entity name is served null and counted in ecartes.opposition, and billing is x402 at $0.05 in USDC/EURC. It even states the citation-reporting obligation, which no structured field carries.

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?

A single dense paragraph, front-loaded with scope and contents, then the null-semantics rule, then edge cases and billing. Every sentence carries information an agent could act on; nothing is padding. Long but justified by the amount of non-obvious behavior it must convey.

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?

Complete for a read-only, open-world, two-parameter tool: contents, null vs zero, prior-year comparatives, GDPR objection handling, 404 billing exemption, price, and citation requirement are all covered. An output schema exists, so further explanation of return shape is unnecessary and appropriately omitted.

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 baseline is 3, but the description adds meaning the schema lacks: date_cloture is specifically the balance-sheet date and must be obtained from list_uk_company_accounts, and company_number keys the Companies House lookup. This is meaningful workflow context beyond the pattern examples in the schema.

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?

Specific verb+resource+scope: 'One UK financial year, with the UK company financial statements decoded from the iXBRL accounts filed at Companies House', then enumerates the exact contents (balance sheet line items, average employees, optional P&L). It is clearly distinct from the sibling list_uk_company_accounts, which it references as the source of the date.

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?

Establishes a clear workflow: 'Balance-sheet date comes from list_uk_company_accounts', telling the agent to enumerate dates before calling this. It also warns that most small companies file a balance sheet only, setting expectations. It stops short of explicit when-not-to-use or failure-handling alternatives beyond the 404 case.

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

Deploy Server

Other Tools