Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Danish annual accounts

get_danish_company_filing
Read-only

Retrieves decoded XBRL annual-report figures for one Danish fiscal year—revenue, results, equity, assets, debts, employees—with prior-year comparatives from the official filing.

Instructions

One Danish fiscal year: financial statements decoded from the company's XBRL annual report (Erhvervsstyrelsen): revenue (null = not published, never zero), gross result, operating result, pre-tax and net result, equity, total assets, debts, average employees, plus prior-year comparatives as published in the same filing. Amounts in the filing currency (mostly DKK); the official XBRL document URL is included. Closing date comes from list_danish_company_filings. Same form check as that tool: a sole proprietorship, an estate or an undecided CVR form returns 404, not billed, as does a number unknown to the CVR or a name under objection (GDPR art. 21). The year's entity name under objection (GDPR art. 21) 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": {
      "id": "<id>",
      "date_cloture": "<date_cloture>"
    },
    "name": "get_danish_company_filing"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes8-digit Danish CVR number
date_clotureYesFiscal-year closing date, YYYY-MM-DD, e.g. 2025-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.6/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it explains that revenue null means not published rather than zero, that refusals are 404 and unpaid, that names under GDPR art. 21 objection are nulled and counted in ecartes.opposition, and that the call is billed $0.05 via x402. The citation requirement is an operational instruction an agent would otherwise miss.

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 resource and returned fields, with billing, refusal conditions, and citation rules trailing in a logical order. It is dense and clause-heavy, but nearly every clause carries information an agent needs; the salary/employee field mention is the only slightly padded item.

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 and annotations already exist, yet the description still supplies the non-obvious pieces: currency caveat, prior-year comparatives, null-vs-zero semantics, error and billing behavior, and the citation obligation. For a paid, read-only filing decode, nothing important is left unexplained.

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, and the description adds genuine meaning on top: it clarifies that date_cloture must be sourced from list_danish_company_filings rather than invented, and ties id to the CVR number used by that sibling. No format details are repeated needlessly.

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: financial statements decoded from a company's XBRL annual report for one Danish fiscal year, then enumerates exactly which line items are returned. It also separates itself from list_danish_company_filings by noting the closing date comes from that tool.

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?

It implicitly routes the agent through list_danish_company_filings to obtain the closing date before calling, and it lists the cases where the call is refused (sole proprietorship, estate, undecided CVR form, unknown number, name under objection). What's missing is an explicit contrast against the country-sibling tools, but the usage context is clear enough to act on.

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