Skip to main content
Glama
robobobby
by robobobby

dk_cvr_search

Search the Danish CVR registry for company details using name, CVR number, P-number, or phone. Retrieve address, industry, employees, owners, and status. Also supports Norwegian companies.

Instructions

Search the Danish CVR registry for a company by name, CVR number, P-number, or phone. Returns company details including address, industry, employees, owners, and status. Also supports Norwegian companies (country=no).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesCompany name, CVR number, P-number, or phone number to search for
search_typeNoSpecific search type. 'auto' (default) searches all fields. 'vat' = CVR number, 'name' = company name, 'produ' = P-number, 'phone' = phone number
countryNoCountry to search in. 'dk' = Denmark (default), 'no' = Norway

Implementation Reference

  • The tool "dk_cvr_search" is registered and implemented here. It takes a query, search_type, and country, processes the parameters, calls `fetchCVR`, and returns the formatted company data.
    server.tool(
      "dk_cvr_search",
      "Search the Danish CVR registry for a company by name, CVR number, P-number, or phone. Returns company details including address, industry, employees, owners, and status. Also supports Norwegian companies (country=no).",
      {
        query: z.string().describe("Company name, CVR number, P-number, or phone number to search for"),
        search_type: z.enum(["auto", "vat", "name", "produ", "phone"]).optional()
          .describe("Specific search type. 'auto' (default) searches all fields. 'vat' = CVR number, 'name' = company name, 'produ' = P-number, 'phone' = phone number"),
        country: z.enum(["dk", "no"]).optional()
          .describe("Country to search in. 'dk' = Denmark (default), 'no' = Norway"),
      },
      async ({ query, search_type, country }) => {
        const params = { country: country || "dk" };
    
        if (search_type && search_type !== "auto") {
          params[search_type] = query;
        } else {
          // Auto-detect: if all digits and 8 chars, likely CVR number
          if (/^\d{8}$/.test(query)) {
            params.vat = query;
          } else {
            params.search = query;
          }
        }
    
        try {
          const data = await fetchCVR(params);
          return { content: [{ type: "text", text: formatCompany(data) }] };
        } catch (err) {
          return { content: [{ type: "text", text: `Error: ${err.message}` }], isError: true };
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions what the tool returns (company details) and supports (Norwegian companies), but lacks critical information such as rate limits, authentication requirements, error handling, or pagination. For a search tool with no annotations, this leaves significant gaps in understanding its operational behavior.

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?

The description is appropriately sized and front-loaded, with two sentences that efficiently convey the tool's purpose, search capabilities, return details, and country support. Every sentence adds value without redundancy, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a search tool with no annotations and no output schema, the description is moderately complete. It covers the basic purpose and usage but lacks details on behavioral traits (e.g., rate limits) and output structure. Without an output schema, it should ideally describe return values more explicitly, but it does mention key details like address and industry, which helps partially compensate.

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?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema by implying the search scope and Norwegian support, but it does not provide additional syntax, format details, or examples. This meets the baseline for high schema coverage without enhancing parameter understanding.

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?

The description clearly states the tool's purpose with specific verbs ('search') and resources ('Danish CVR registry for a company'), and it distinguishes itself from siblings like 'dk_cvr_lookup' by emphasizing search functionality across multiple fields (name, CVR, P-number, phone) rather than a direct lookup. It also explicitly mentions support for Norwegian companies, which is unique among the sibling tools.

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?

The description provides clear context on when to use this tool by specifying the types of queries (name, CVR, P-number, phone) and countries (Denmark, Norway). However, it does not explicitly state when not to use it or name alternatives, such as 'dk_cvr_lookup' for direct CVR lookups or other country-specific tools, leaving some ambiguity in sibling differentiation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/robobobby/mcp-nordic'

If you have feedback or need assistance with the MCP directory API, please join our Discord server