Skip to main content
Glama

Search Danish companies by name

search_company
Read-onlyIdempotent

Find a Danish company's CVR number by name or verify a CVR number in the CVR register. Use it first when you only have a name, because other tools require the CVR number.

Instructions

Find a Danish company's CVR number by name (or check a CVR number) in the CVR register. Use it first when you only have a name; every other tool needs the CVR number. Matches all words of the query against current company names; returns name, status, company type, industry, address and employee size band, with active, exactly named and larger companies first. Needs CVR_USER and CVR_PASSWORD in the server's environment (free system-to-system access to the CVR register); without them it returns an error saying how to get access.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of companies to return.
queryYesCompany name or part of it, e.g. "Carlsberg" or "lego a/s". An 8-digit CVR number looks up that company.

Output Schema

NameRequiredDescriptionDefault
companiesYesActive companies first, then exact name matches, then the largest; empty when nothing matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.2
    • changedOutput schema / properties / companies / description
      Previous value: -"Best matches first; empty when nothing matches."New value: +"Active companies first, then exact name matches, then the largest; empty when nothing matches."
    • addedOutput schema / properties / companies / items / properties / employees
      Added value: +{
      +  "description": "Size band from the register's latest monthly employment figures, e.g. \"200-499\" or \"1000+\".",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / companies / items / required
      Previous value: -[
      -  "cvr",
      -  "name",
      -  "status",
      -  "companyType",
      -  "industry",
      -  "address"
      -]New value: +[
      +  "cvr",
      +  "name",
      +  "status",
      +  "companyType",
      +  "industry",
      +  "address",
      +  "employees"
      +]
  2. Addedv0.3.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description adds behavior they cannot: all-words matching against *current* names, the result ordering (active, exact-name, larger first), the credential requirement (CVR_USER/CVR_PASSWORD) and the specific error surfaced when they are absent. That is rich operational context beyond the structured fields.

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 tight sentences, each doing distinct work: purpose, routing priority, match/sort semantics, and auth requirement. Scope and the "use first" directive are front-loaded before the operational details.

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?

An output schema exists, yet the description still previews the returned fields, and it covers the auth prerequisite and failure mode that would otherwise block a successful call. Nothing an agent needs to invoke this 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%, so both parameters are already documented and baseline is 3. The description adds meaning the schema does not: the match is against all words of the query and only current company names, which tells the agent how to phrase a query and why a miss may occur.

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 (find a company's CVR number by name) plus a secondary mode (check a CVR number) in a named register. It explicitly frames itself as the entry point that the sibling tools (get_financials, list_filings) depend on, so the agent can distinguish it from them without opening a 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?

"Use it first when you only have a name; every other tool needs the CVR number" names the condition that selects this tool and implicitly excludes all siblings until a CVR number exists. Nothing about ordering or prerequisites is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.