Skip to main content
Glama

SelskabsInfo — Danish company data

Search people in the Danish company register

search_persons
Read-only

Search people registered in Danish companies by name; part of a name works, and small misspellings are tolerated. Returns candidates, each with the unit number (enhedsnummer) get_person needs, the number of current and former company roles, and up to three of their current companies. Danish names are often shared — compare those companies before concluding two hits are the same person. 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": {
      "query": "<query>"
    },
    "name": "search_persons"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum matches to return (max 50). There is no paging beyond this.
queryYesThe person's name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Adds meaningful context beyond the read-only annotations: result contents, the name-collision caveat, and plan availability. It does not discuss rate limits or other operational constraints, but with safety annotations already present this is a substantial disclosure.

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 tightly packed sentences, front-loaded with purpose and search behavior, followed by return details and disambiguation guidance. Every sentence earns its place.

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, so the description appropriately explains the return payload: unit number, role counts, and sample current companies. Combined with the ambiguity warning, it gives an agent enough context to call and interpret the tool correctly.

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 real semantic value for the query parameter by clarifying that partial names and small misspellings are tolerated.

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 ('Search people registered in Danish companies by name') and clearly distinguishes this lookup from detail-oriented siblings like get_person by explaining that results carry the enhedsnummer get_person needs.

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?

Gives useful search behavior (partial names work, misspellings tolerated) and routes the agent toward get_person for details. It stops short of an explicit when-not-to-use statement or a direct comparison with search_companies, so it is strong but not fully exhaustive.

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