Skip to main content
Glama

SelskabsInfo — Danish company data

Get subsidiaries of a Danish company

get_subsidiaries
Read-only

Companies that one Danish company owns, with the ownership band for each. Looked up by CVR number (use search_companies first when you only have a name). Costs 2 credits: the base lookup plus this section. When the user also needs the company profile or more than one section, one get_company call with sections is cheaper and faster than several section tools. If the caller's plan does not include the section, the call is refused at no cost with tier_restricted; tell the user it is not in their current plan rather than reporting the data as absent.

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

Input Schema

NameRequiredDescriptionDefault
cvrYesThe 8-digit Danish CVR number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description goes further by disclosing the 2-credit cost model and that a plan-restricted call is refused at no cost with tier_restricted. It does not describe what the returned list entries contain beyond the ownership band, nor what an empty result means, which keeps it short of a 5.

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?

Four sentences, each doing distinct work: what it returns, how to resolve the key, what it costs, and what to do instead or on refusal. The most decision-relevant fact (cost/alternative) is placed after the identification sentence rather than buried.

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 one-parameter read tool with annotations and no output schema, the description covers identification, key resolution, pricing, alternative routing, and error semantics. Nothing an agent needs in order to select and invoke it correctly is missing.

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% and the single parameter already carries a pattern and the '8-digit Danish CVR number' description, so the baseline is 3. The description adds real meaning by implying a CVR must be resolved first ('use search_companies first when you only have a name'), telling the agent how to obtain a valid value.

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?

Starts with a concrete verb-phrase resource: 'Companies that one Danish company owns, with the ownership band for each,' which fixes the ownership direction downward. It is implicitly distinct from upward-looking siblings (get_ownership, get_real_owners, get_ultimate_owners) but never names them, so an agent deciding between ownership tools must still reason from the phrasing alone.

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?

Gives explicit prerequisites ('use search_companies first when you only have a name') and an explicit alternative with its trigger condition ('when the user also needs the company profile or more than one section, one get_company call with `sections` is cheaper'). It also covers the refused-call case so the agent knows how to report tier_restricted rather than as absent data.

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