Skip to main content
Glama

SelskabsInfo — Danish company data

Get a person and their company roles

get_person
Read-only

A person's roles in Danish companies as the Danish Central Business Register (CVR) records them: the companies they direct, sit on the board of, founded or are registered as a legal owner of, current and former, each with the role and its dates. Look the person up by the unit number (enhedsnummer) that search_persons returns. A legal-owner role is titled "LEGAL EJER", with its ownership band in ejerandel. Business roles only: no home address or other contact details. Capped at 100 company relations. Not in every plan.

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": {
      "id": "<id>"
    },
    "name": "get_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe person unit number (enhedsnummer) returned by search_persons.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare a safe read (readOnlyHint true, destructiveHint false, openWorldHint true), and the description adds genuinely new context: a hard cap of 100 company relations, inclusion of historical/former roles, and an availability caveat ('Not in every plan'). What it does not cover is how truncation is signalled when the 100-relation cap is hit.

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 scope constraint and role enumeration come first, then lookup instructions, then caveats — a sensible front-loaded order with no filler. The opening sentence is dense and heavily nested, which costs a point but nothing is truly redundant.

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 supplies everything an agent needs: what is returned (roles with dates, LEGAL EJER bands), what is excluded (contact details), the lookup key source, the size limit, and plan availability.

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?

With a single parameter at 100% schema description coverage, the schema already explains that id is the person unit number (enhedsnummer) returned by search_persons. The description repeats that same fact rather than adding format or validation nuance, so the baseline 3 applies.

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-and-resource pairing: retrieves a person's company roles as recorded by the Danish CVR, enumerating the role types (director, board, founder, legal owner) plus current and former status. This clearly separates it from company-centric siblings like get_management, get_ownership and get_real_owners.

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?

Explicitly tells the agent to obtain the id from search_persons first, which is the key prerequisite. It also implicitly routes away from contact use cases with 'Business roles only: no home address or other contact details', though it never names a sibling such as get_contact_details as the alternative.

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