Skip to main content
Glama

Danish Company Info by SelskabsInfo

Get a Danish company

get_company
Read-only

Get full details for one Danish company by CVR number. The base response covers name, status, address, industry, employees, capital, purpose and name/status history. Take it when the user wants the profile with one or more sections, or several sections at once: it costs 1 credit plus 1 per section, while each section tool (get_financials, get_management, get_ownership and the rest) costs 2 on its own. For one section alone, its section tool returns the same data in a smaller answer. Request additional sections only when needed — each one costs an extra API credit and adds latency: • financials — annual accounts (up to four years): revenue, EBIT, EBITDA, profit, equity, balance sheet and key ratios, each year with a link to its filed report • management — directors, board, founders and auditors, plus any liquidator or association representatives • ownership — legal owners from the ownership register (banded percentages, e.g. "25-33%") • realOwners — beneficial owners (UBO). Confidential data: requires a signed contract with SelskabsInfo • subsidiaries — companies this one owns • creditRisk — SI-score (0-10), an algorithmic risk score, not a credit rating, with warnings and critical flags • capital — capital events: formation, increases, reductions, with rate and valuation • courtData — civil court cases plus decisions and notices from 8 authorities and boards and Statstidende. Large; request only when the user asks about legal or regulatory history. Sections the caller's plan does not include are skipped rather than failing the call, and the response lists them under "warnings" — tell the user which sections were left out because they are not in their current plan.

Input Schema

NameRequiredDescriptionDefault
cvrYesThe 8-digit Danish CVR number.
sectionsNoExtra sections to include. Omit for the base profile. Each section costs one extra credit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses pricing structure, per-section latency, plan-based section skipping with warnings, confidential UBO access requirements, and the large size of courtData. These are meaningful operational traits an agent cannot infer from the schema or annotations.

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 long but front-loaded and well-structured: the core behavior and cost tradeoff come first, followed by a bulleted section breakdown. Every sentence earns its place by helping the agent decide which sections to request.

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?

For a complex tool with no output schema, the description is complete enough: it explains the base response fields, the optional sections, cost implications, plan-skip warnings, and confidential-access caveats. An agent has what it needs to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already has 100% coverage, the description adds substantial meaning to each section value: what financials, management, ownership, realOwners, subsidiaries, creditRisk, capital, and courtData actually return. It also clarifies that omitted sections yield the base profile and that extra sections cost one credit each.

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 states a specific verb and resource: get full details for one Danish company by CVR number. It immediately distinguishes the tool from section-specific siblings such as get_financials and get_management.

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?

It gives explicit selection guidance: use this tool when the user wants the profile with one or more sections, use a section tool when only one section is needed, and request extra sections only when needed because each adds cost and latency. It also explains plan-based skipping behavior and the realOwners contract requirement.

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