Skip to main content
Glama

Danmark Data

Company annual accounts

company_financials
Read-onlyIdempotent

Key figures from the latest published annual reports (revenue, gross profit, profit before tax, result, assets, equity) in DKK, with a link to the filed report.

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": "company_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
cvrYes8-digit CVR number

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world access. The description adds real behavioral context beyond them: only the LATEST published report is returned (not history), figures are denominated in DKK, and a link to the filed report is included.

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?

A single sentence that front-loads the data source and then lists the returned fields in parentheses. No filler, no repetition of structured metadata.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 explained, and the single required parameter is fully documented. The description covers source, scope, currency and the report link; the only real gap is what happens when a company has no published accounts.

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?

There is one parameter with 100% schema description coverage ('8-digit CVR number'), so the schema carries the parameter documentation. The description adds nothing about the identifier's format or behavior, which is acceptable but not additive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (key figures from the latest published annual reports) and enumerates the exact fields returned (revenue, gross profit, profit before tax, result, assets, equity) plus currency. It does not explicitly distinguish itself from siblings like get_company, but the purpose is unambiguous.

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 only implied: an agent can infer this is the tool for financial figures when annual-report data is needed. There is no explicit when-to-use statement, no exclusion such as 'use get_company for general company data', and no note about prerequisites like the company having filed a report.

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