danish-cvr
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cvr_searchA | 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). |
| cvr_lookupA | Look up a specific Danish company by its 8-digit CVR number. Returns full company details. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| usage |
TDQS
Scored across 2 tools
The two tools both return company details, and cvr_search supports lookup by CVR number, which overlaps with cvr_lookup's specific purpose. However, the descriptions clarify that cvr_lookup is for exact CVR lookups while cvr_search is broader, reducing some ambiguity.
Both tools follow the same cvr_<verb> pattern, using clear, consistent snake_case naming. The verb prefixes 'search' and 'lookup' are semantically appropriate.
With only two tools, the server feels thin for a registry API, but the two operations cover the core lookup scenarios. The count is borderline but not extreme.
Search by multiple identifiers and direct CVR lookup cover the primary read-only use cases for a public company registry. No mutating operations are expected, so the surface seems largely complete, though additional specialized queries could be added.