Skip to main content
Glama

SelskabsInfo — Danish company data

Get capital history, cap tables and M&A of a Danish company

get_capital_overview
Read-only

Capital history of one Danish company as the SelskabsInfo due diligence report shows it. Every formation, capital increase (each tranche on its own), reduction and ownership change without a capital change (M&A), with the subscription rate (kurs), price per share, subscription amount (tegningsbeloeb), payment type and post-money valuation; the owners at each round as the ownership register's bands; who left, entered or changed band in each ownership change; per round an estimated cap table (shares before and after, new shares, estimated investment per owner) and the likely investors; an accumulated cap table (each owner's band in each round); and statistics (total raised, largest and average round, raised per year, highest and latest valuation, months since the latest raise). Amounts are in each round's "valuta" (DKK for almost every company; "valutaer" lists every currency the capital has had), so name that currency rather than assume kroner. Share counts and investments are estimates from the bands at a nominal value of 1 per share in that currency unless the registration text says otherwise, so present them as estimates and relay "forbehold". "kursOplyst": false means no rate was registered and par is assumed. An ownership change has no price: the purchase price is not public. The rounds are listed oldest first; a long history keeps the most recent 20 and says so. Not in every plan; costs 3 credits. When the caller's plan does not include it, get_capital_events lists the registered capital changes alone.

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_capital_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
cvrYesThe 8-digit Danish CVR number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint=true annotations, it discloses plan gating, a 3-credit cost, currency semantics (use 'valuta', don't assume DKK), that share counts/investments are estimates at nominal value 1 and must be presented with 'forbehold', that kursOplyst:false means par is assumed, that ownership changes carry no public price, and that history is truncated to the latest 20 rounds. This is unusually rich behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is nearly all useful, but it is delivered as one enormous run-on sentence with semicolon chains, which is hard to parse. Front-loading the resource is good, yet structure could be segmented into scannable sentences.

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?

No output schema exists, and the description compensates by detailing every returned section (rounds, per-round cap table, accumulated cap table, statistics), plus caveats on estimates, currency, and truncation. Nothing essential for correct interpretation is missing.

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?

Only one parameter (cvr) and schema coverage is 100%, so the schema already documents it fully; the description adds nothing about the parameter itself. Baseline 3 applies since the schema does the work.

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+resource (capital history of one Danish company) and enumerates the exact content: formations, increases per tranche, reductions, ownership changes, cap tables, valuation statistics. An agent can distinguish it from get_capital_events and get_ownership without opening any schema.

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?

Explicitly names the fallback ('When the caller's plan does not include it, get_capital_events lists the registered capital changes alone') and flags availability/cost constraints ('Not in every plan; costs 3 credits'). This gives both a when-to-use and a when-not/alternative path.

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