Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Finnish annual accounts (PRH)

get_finnish_company_filing
Read-only

Retrieve a Finnish company's fiscal-year financial statements by Business ID and closing date from its PRH XBRL filing, including revenue, results, equity, assets, debts, and comparatives.

Instructions

One Finnish fiscal year, with its financial statements decoded from the company's PRH XBRL filing: revenue (null = not published, never zero), operating and net result, equity, total assets, debts, plus the prior-year comparatives as published in the same filing (EUR). Closing date comes from list_finnish_company_filings. Paid via x402 ($0.15 in USDC or EURC). FI accounts are served only for a company the live PRH profile serves, as /evenements: a Business ID unknown to the PRH (a sole trader, toiminimi, or a name under objection) gets the profile's 404 (entreprise_inconnue), a company form that does not prove a legal person (branch of a foreign trader) gets forme_juridique_non_servie, a PRH outage gets 503; never billed (rule R1). 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": {
      "id": "<id>",
      "date_cloture": "<date_cloture>"
    },
    "name": "get_finnish_company_filing"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFinnish Business ID (Y-tunnus), NNNNNNN-N
date_clotureYesFiscal-year closing date, YYYY-MM-DD, e.g. 2024-12-31

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.8/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses semantics the annotations cannot: revenue null means not published and never zero, costs ($0.15 in USDC or EURC via x402), and that failed lookups are never billed under rule R1. It also imposes an output obligation (cite `citation` verbatim), which is behavior an agent must know before calling.

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-loads what is returned before pricing, failure modes, and the citation rule, and nearly every clause carries operative information. It is a dense single block rather than a structured list, and the internal reference 'as /evenements' is jargon that costs a little reading effort without adding agent-facing meaning.

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?

An output schema exists, so return values need not be re-explained, and the description instead covers the things structured fields cannot: prerequisites, null semantics, cost, and the exact failure modes and their non-billing behavior. Nothing an agent needs in order to call this correctly appears to be missing.

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% (both parameters documented with patterns and examples), so the baseline is 3. The description adds provenance for date_cloture — it must be taken from list_finnish_company_filings — which prevents the agent from guessing a fiscal year end, plus independent null semantics for the revenue value returned for that period.

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 resource and scope — one Finnish fiscal year with financial statements decoded from the PRH XBRL filing — and enumerates the returned line items (revenue, operating/net result, equity, assets, debts, prior-year comparatives, EUR). It explicitly points to the sibling list_finnish_company_filings as the source of the closing date, so the agent can separate this from the listing tool without opening either schema.

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?

Gives a concrete prerequisite (closing date must come from list_finnish_company_filings), names when the tool cannot be used (Business ID unknown to PRH, non-legal-person company forms, PRH outage) with the exact error identifiers, and states the billing consequence for each. That is explicit when-to-use and when-not guidance rather than implied context.

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