Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Finnish trade-register notices (PRH)

get_finnish_company_events
Read-only

Retrieve Finnish company trade-register notices from PRH open data by Business ID, including notice types, register entry codes, and bankruptcy, restructuring, or liquidation summaries.

Instructions

Finnish company trade-register notices from the PRH open data (avoindata.prh.fi, CC BY 4.0, live with a 24 h cache): every notice registered since late 2014, newest first: date, record number, notice type (creation, modification, comptes_annuels, rectification, fusion; source code always served) and the register entry codes it carries, each with the PRH labels in EN/FI/SV and a closed-list family (direction, representation, capital, shares, registered office, auditors, articles, bankruptcy, restructuring, liquidation, removal, merger, demerger…); procedures_inscrites summarises bankruptcy / restructuring / liquidation / removal codes with their latest date; register memberships (trade register, VAT, prepayment, employer) with dates and tva_active. Codes and dates only, never a person. Unknown Business ID, a foreign trader's branch, a form outside the YRMU codebook or a current name under objection (GDPR art. 21) = 404 (no charge). Paid via x402 ($0.02 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": {
      "id": "<id>"
    },
    "name": "get_finnish_company_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFinnish Business ID (Y-tunnus), NNNNNNN-N, e.g. 0112038-9

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.3/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 goes far beyond them: data freshness (24 h cache, live), licensing, pricing via x402 ($0.02 USDC/EURC), the exact 404 conditions including 'no charge', and the GDPR art. 21 name-objection case. It also discloses the shape of returned data (codes and dates only, never a person), which is materially useful behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded correctly with source and content, and every clause carries information, but it is a single dense run-on packed with semicolons and parentheticals that is harder to scan than it needs to be. Some license/attribution detail could be moved or trimmed.

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?

Given an output schema already exists, the description does not need to restate return values and instead covers what structured fields cannot: error semantics, freshness, pricing, and attribution requirements. Nothing an agent needs in order to call it and interpret a 404 is 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?

The single parameter is fully documented in the schema (pattern, example), so the baseline is 3; the description adds semantic value by stating that an unknown Business ID yields a 404 with no charge, telling the agent what an unmatched ID actually does. It does not go further into ID formatting beyond what the schema already specifies.

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?

Opens with a specific verb+resource+scope: 'Finnish company trade-register notices from the PRH open data', names the upstream source, and immediately enumerates what each notice contains (date, record number, notice type, entry codes). An agent can distinguish it from the many sibling country-register and filing tools without opening the schema.

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 is implied by the data description (register notices since late 2014, newest first), and useful negative conditions are given for 404s (unknown Business ID, foreign branch, name under objection). However, it never explicitly routes the agent between this tool and the nearby siblings such as get_finnish_company_filing or list_finnish_company_filings, so the when-to-use decision is left to inference.

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