Skip to main content
Glama

Hent regnskab

hent_regnskab
Read-onlyIdempotent

Nøgletal fra årsrapporterne pr. år, nyeste først: omsætning, bruttofortjeneste, resultat, egenkapital, balance, soliditetsgrad og ansatte. Selskabets egne tal; har selskabet et koncernregnskab, står det for sig i koncernregnskaber. Beløb i hele kroner (feltet valuta er sat, hvis regnskabet ikke er i DKK). Mange små selskaber oplyser ikke omsætning (kun bruttofortjeneste). Hvor rapporten oplyser det: revisionsfirma, revisors konklusion (kun hvis ikke uden forbehold), foreslået udbytte, gæld til tilknyttede virksomheder, kapitalforhøjelse og godkendelsesdato. Årsrapporter uden læsbare tal (kun PDF) står med link i andre_dokumenter. Feltet skat har Skattestyrelsens åbne skattelister pr. indkomstår (skattepligtig indkomst, underskud, selskabsskat og sambeskatning), når selskabet står på listerne; skattepligtig indkomst er ikke det samme som årets resultat. Eksempel: {"cvr": "10150817", "aar": 3}. Kræver betalt pakke (gratis nøgle: smagsprøver). Tæller 1 opslag.

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": {
      "cvr": "<cvr>"
    },
    "name": "hent_regnskab"
  }
}

Input Schema

NameRequiredDescriptionDefault
aarNoAntal regnskabsår, nyeste først (standard 3).
cvrYesCVR-nummer med 8 cifre, fx "10150817". Kender du kun navnet, så brug soeg_virksomhed først.
detaljerNo"kort" (standard) giver de vigtigste felter. "fuld" giver alle felter.kort

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for adding what annotations cannot: a credit/quota cost ('Tæller 1 opslag'), a paywall requirement, currency semantics for non-DKK reports, and real data-availability caveats (small companies often omit revenue; PDF-only reports land in andre_dokumenter). It stops short of describing error behavior for an invalid CVR or what an empty result looks like.

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 returned fields, followed by qualifications that each carry information — consolidated accounts, currency, reporting gaps, the tax-list caveat distinguishing skattepligtig indkomst from årets resultat, then cost. It is a dense single block without structural separation, and the tax-field passage is long relative to its importance, but little is truly redundant.

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?

There is no output schema, so the description carries the return-value burden itself and does so thoroughly: field list, ordering, currency field, consolidated-account separation, supplementary fields, and the fallback for PDF-only filings. For a 3-parameter read tool this is enough for an agent to call it correctly and interpret the result.

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 coverage is 100%, so all three parameters are already documented, including the 'kort'/'fuld' enum, and this becomes the baseline. The description adds an end-to-end example call and implicitly confirms year ordering ('nyeste først'), but says nothing about what 'detaljer' actually changes or how 'aar' interacts with sparse filings.

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 key figures from annual reports, per year, newest first) and enumerates the exact fields returned (omsætning, bruttofortjeneste, resultat, egenkapital, balance, soliditetsgrad, ansatte). It also clarifies scope — own-company figures versus separate consolidated accounts — so an agent can distinguish it from a general company-lookup or full-report sibling.

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 content (retrieve financials for one company) and the paid-package note gives a cost precondition, but there is no explicit when-to-use/when-not guidance and no named alternative such as a credit-rating or full-report tool. The only sibling hint, 'brug soeg_virksomhed først' when you only know the name, lives in the schema field description rather than the tool description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources