Skip to main content
Glama

Denmark company

run_dk_companies
Read-onlyIdempotent

Get one company from the Denmark registry (CVR) by registration number or registry URL: name, status, registration date, address and legal form. Flat 5 points per successful run.

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": {
      "company": "<company>"
    },
    "name": "run_dk_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesRegistration number or registry URL. e.g. 24256790

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint, non-destructive), so the bar is lower. The description adds genuinely new behavior beyond structured fields: the concrete field set returned (name, status, registration date, address, legal form) and the billing behavior ('Flat 5 points per successful run'), which is useful cost context. It does not cover auth or not-found 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?

Two short clauses with zero waste; the purpose and input modes are front-loaded and the cost note is appended compactly. Every phrase earns its place.

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

Completeness4/5

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

With no output schema, the description usefully enumerates the returned fields, and annotations cover the safety profile, so an agent has what it needs to call it. It stops short of covering failure/not-found behavior or the search-vs-lookup routing, leaving a small gap.

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% and the single 'company' parameter already documents both accepted forms with an example. The description restates the same input modes without adding syntax or format detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Get one company from the Denmark registry (CVR)') and the input modes (registration number or registry URL), plus the returned fields. The singular 'one company' implicitly distinguishes it from run_dk_companies_search, but the sibling is never named, so differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage (exact lookup by registration number or URL) but never states when to prefer this over run_dk_companies_search or run_dk_company_filings, nor any exclusion. Context is implied rather than explicit.

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