dk-regnskab-mcp

Get key financials from an annual report

get_financials

Read-onlyIdempotent

Retrieve a Danish company's key figures (revenue, profit, equity, assets, cash, employees, auditor) for a given year and the prior year using its CVR number. Ideal for one year's headline numbers.

Instructions

Read one annual report (XBRL) of a Danish company and return its key figures for that year and the year before: revenue, gross profit, operating profit, profit, equity, assets, cash, employees, plus company name, period, currency and auditor. Use it for one year's headline numbers; use get_financials_history for a trend over several years and get_report_facts for any other line item. Group reports default to the consolidated group. Values are in the filing's currency (usually DKK); a missing figure is null and notes say why (small companies may legally omit revenue). found=false when the company has no machine-readable annual report for that year.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cvr`	Yes	Danish CVR number, 8 digits (spaces, dashes and a DK prefix are accepted), e.g. "24256790".
`year`	No	Calendar year the reporting period ends in (a 2024/25 financial year ending June 2025 is 2025). Omit for the latest annual report.
`scope`	No	For group reports (koncernregnskab): "group" = the consolidated group, "parent" = the parent company alone. Ignored for single companies.	group

Output Schema

TableJSON Schema

Name	Required	Description
`cvr`	No
`name`	No
`found`	Yes
`notes`	No	Gaps, conflicts and caveats found in the filing, in plain English.
`scope`	No	Whose figures these are; "company" for a report without a group.
`period`	No	Reporting period, ISO dates.
`source`	No	The filing document the figures were read from.
`auditor`	No
`figures`	No	Key figures; current = this report's year, previous = the year before.
`message`	No	Why nothing was found (only when found=false).
`currency`	No
`taxonomy`	No
`reportType`	No
`groupReport`	No
`previousPeriod`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.3.1Sep 26, 2026

changedInput schema / properties / cvr / description

Previous value: -"Danish CVR number, 8 digits (spaces, dashes and a DK prefix are accepted)."New value: +"Danish CVR number, 8 digits (spaces, dashes and a DK prefix are accepted), e.g. \"24256790\"."

changedInput schema / properties / scope / description

Previous value: -"For group reports (koncernregnskab): the consolidated group, or the parent company alone. Ignored for single companies."New value: +"For group reports (koncernregnskab): \"group\" = the consolidated group, \"parent\" = the parent company alone. Ignored for single companies."

changedInput schema / properties / year / description

Previous value: -"Calendar year the reporting period ends in. Omit for the latest annual report."New value: +"Calendar year the reporting period ends in (a 2024/25 financial year ending June 2025 is 2025). Omit for the latest annual report."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "auditor": {
+      "additionalProperties": false,
+      "properties": {
+        "assistance": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "firm": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "firm",
+        "assistance"
+      ],
+      "type": "object"
+    },
+    "currency": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "cvr": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "figures": {
+      "description": "Key figures; current = this report's year, previous = the year before.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "current": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "key": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "previous": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "key",
+          "label",
+          "current",
+          "previous"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "groupReport": {
+      "type": "boolean"
+    },
+    "message": {
+      "description": "Why nothing was found (only when found=false).",
+      "type": "string"
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "notes": {
+      "description": "Gaps, conflicts and caveats found in the filing, in plain English.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "period": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "end": {
+              "type": "string"
+            },
+            "start": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "start",
+            "end"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Reporting period, ISO dates."
+    },
+    "previousPeriod": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "end": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "start": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "required": [
+            "start",
+            "end"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "reportType": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "scope": {
+      "description": "Whose figures these are; \"company\" for a report without a group.",
+      "enum": [
+        "group",
+        "parent",
+        "company"
+      ],
+      "type": "string"
+    },
+    "source": {
+      "additionalProperties": false,
+      "description": "The filing document the figures were read from.",
+      "properties": {
+        "documentType": {
+          "type": "string"
+        },
+        "publishedAt": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "publishedAt",
+        "documentType",
+        "url"
+      ],
+      "type": "object"
+    },
+    "taxonomy": {
+      "enum": [
+        "danish-gaap",
+        "ifrs",
+        "unknown"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "found"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv0.2.0Sep 24, 2026

addedInput schema / properties / scope

Added value: +{
+  "default": "group",
+  "description": "For group reports (koncernregnskab): the consolidated group, or the parent company alone. Ignored for single companies.",
+  "enum": [
+    "group",
+    "parent"
+  ],
+  "type": "string"
+}

First observedv0.1.0Sep 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds valuable behavioral context beyond annotations: it explains missing figures are null with notes, small companies may omit revenue, and found=false indicates no machine-readable report. It does not contradict annotations and enriches the agent's understanding of edge cases.

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?

The description is well-structured and efficient. It front-loads the core purpose, then lists the return fields, then gives usage guidance, and finally notes edge cases. Every sentence contributes necessary information without redundancy, achieving conciseness while being thorough.

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?

The tool has an output schema, so return structure is documented there. The description covers all essential aspects: what it returns, when to use it versus siblings, default scope, currency, missing-value behavior, and the found=false condition. It is complete for an agent to decide when to call it and what to expect, without needing external details.

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?

Schema description coverage is 100%, so parameters are fully documented in the schema. The description does not add significant extra semantics beyond what the schema already provides; it reiterates defaults and formats. Given the high coverage, a baseline of 3 is appropriate, as the description adds minimal value beyond 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?

The description clearly states the tool reads one annual report and returns specific key figures, naming the exact financial items. It explicitly distinguishes from siblings by saying 'Use it for one year's headline numbers; use get_financials_history for a trend over several years and get_report_facts for any other line item.' This makes the purpose unambiguous and differentiates it.

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?

The description gives explicit guidance on when to use this tool versus alternatives: 'Use it for one year's headline numbers; use get_financials_history for a trend over several years and get_report_facts for any other line item.' It also explains the default scope for group reports and notes that omitted year retrieves the latest report, giving clear context for invocation.

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

Deploy Server