Skip to main content
Glama

SelskabsInfo — Danish company data

Find the ultimate owners of a Danish company

get_ultimate_owners
Read-only

Who ultimately owns one Danish company. Follows the legal ownership chain through holding companies until it reaches people, and reports each person with the routes of companies that lead to them and the ownership band at every link. Also lists the directors with whether each one is a direct owner, the largest direct owner, an ultimate owner, or the sole ultimate owner, so "is this privately owned?" and "is the director the main shareholder?" are answered in one call. Uses the public ownership register (legal owners, banded percentages such as "50-66%"), not the confidential beneficial-owner register, so no contract is needed. Looked up by CVR number (use search_companies first when you only have a name). Costs 3 credits for the company plus 2 per holding company followed; it follows at most max_depth levels (default 3) and 12 companies, and lists under "uafklaret" what it could not resolve: owners without a Danish CVR number, the depth and company limits, the time one call may take. A company with no registered owners, such as a foundation, ends its chain and is listed among the ultimate owners with a note. Long lists are capped, with a "_truncated" key giving the full count. Companies with no ownership register (sole proprietorships, partnerships) come back with no owners; their company form says they are personally owned. It reads the ownership section, which is not in every plan; when the caller's plan does not include it, the call is refused at no cost.

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

Input Schema

NameRequiredDescriptionDefault
cvrYesThe 8-digit Danish CVR number.
max_depthNoHow many levels of holding companies to open above the company. 1 opens only the holding companies that own it directly; the default of 3 covers nearly every Danish group.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description adds substantial behavior beyond annotations: it discloses credit costs, maximum depth and company limits, truncated-list behavior via a _truncated key, unresolved items under 'uafklaret', foundation handling, no-register company forms, and plan-based refusal at no cost. These are meaningful operational and failure-mode details that an agent could not infer from the read-only annotations alone.

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?

The description is front-loaded with the core purpose and then adds operational details, with nearly every sentence carrying useful information. It is dense and somewhat run-on, but the length is justified by the complexity of ownership-chain traversal, costs, limits, and edge cases.

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 burden of explaining return behavior, and it does so thoroughly: ownership routes, ownership bands, director classifications, unresolved items, truncation, foundations, and companies without an ownership register. An agent has enough information to call the tool and interpret its likely outputs.

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 the schema already documents both parameters. The description adds useful semantic context by explaining that max_depth controls how many holding-company levels are opened and that each followed holding company increases cost, which goes beyond the schema's existing explanation.

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: it finds who ultimately owns one Danish company by following the legal ownership chain through holding companies to people. It clearly distinguishes this from related capabilities by explaining that it returns ownership routes, ownership bands at each link, and director ownership status, all in one call.

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?

The description gives clear usage context, including lookup by CVR number and to use search_companies first when only a name is available. It also distinguishes the public ownership register from the confidential beneficial-owner register, but it does not explicitly name sibling alternatives such as get_ownership or get_real_owners and when to prefer them.

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