Skip to main content
Glama
robobobby
by robobobby

dk_cvr_lookup

Look up Danish companies by CVR number to retrieve full business details including registration information and company data.

Instructions

Look up a specific Danish company by its 8-digit CVR number. Returns full company details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cvr_numberYes8-digit CVR number
countryNo'dk' (default) or 'no'

Implementation Reference

  • The implementation of the `dk_cvr_lookup` tool, which takes a CVR number and country code to fetch company data.
    server.tool(
      "dk_cvr_lookup",
      "Look up a specific Danish company by its 8-digit CVR number. Returns full company details.",
      {
        cvr_number: z.string().regex(/^\d{8}$/).describe("8-digit CVR number"),
        country: z.enum(["dk", "no"]).optional().describe("'dk' (default) or 'no'"),
      },
      async ({ cvr_number, country }) => {
        try {
          const data = await fetchCVR({ vat: cvr_number, country: country || "dk" });
          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. It mentions that it 'Returns full company details', which adds some behavioral context about output, but it doesn't disclose other traits like rate limits, authentication needs, error handling, or whether it's read-only/destructive. This is inadequate for a tool with no annotation coverage.

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 a single, efficient sentence that front-loads the key information (look up by CVR, returns details). There's no wasted text, and it's appropriately sized for the tool's complexity.

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 no annotations and no output schema, the description is minimal but covers the basic purpose. It doesn't fully compensate for the lack of behavioral details or output information, making it adequate but with clear gaps for a lookup tool.

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 fully documents both parameters. The description doesn't add any parameter semantics beyond what's in the schema (e.g., it doesn't explain the 'country' parameter's relevance or default behavior). Baseline 3 is appropriate when the schema does the heavy lifting.

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 a specific verb ('Look up') and resource ('Danish company'), and it distinguishes from sibling tools like 'dk_cvr_search' by specifying it's for looking up a specific company by CVR number rather than searching.

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 implies usage context by specifying 'Danish company' and 'CVR number', but it doesn't explicitly state when to use this tool versus alternatives like 'dk_cvr_search' or other country-specific company lookup tools. It provides clear prerequisites but lacks explicit alternatives.

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