Skip to main content
Glama

SelskabsInfo — Danish company data

Check a Danish VAT number

get_vat_status
Read-only

Check whether DK plus a CVR number is a valid, active VAT number, and get the name and address the VAT register holds for it, which is worth comparing with the CVR name when verifying a counterparty. Answers in two fields, and the difference between them matters: "momsnummerGyldigt" is the register's literal answer about the NUMBER and is what an invoicing decision turns on, while "momsregistreret" is the inference about the COMPANY and is never false, because a group company in a joint registration settles VAT under another SE number and so shows up as invalid while plainly being VAT registered. Never tell a user a company is not VAT registered on the strength of an invalid number: say the number is not valid, and read the "forbehold" field aloud. VAT registration is not held in the CVR register at all, so this answer comes from a different source than every other tool here and can differ from it. Not in every plan; costs 1 credit. A momentary failure at the VAT register returns an error rather than a guessed "no", so treat an error as "unknown" and try again.

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": {
      "cvr": "<cvr>"
    },
    "name": "get_vat_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
cvrYesThe 8-digit Danish CVR number. The VAT number checked is DK plus this number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the read-only annotations by explaining the two answer fields and their critical difference, warning against telling a user a company is not VAT registered based on an invalid number, pointing to the forbehold field, noting the separate data source, and clarifying that a register error means 'unknown' rather than 'no'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core purpose and the key field distinction. It is fairly long and dense, but every sentence carries a non-obvious operational caveat, so the length is largely earned; minor tightening could still improve readability.

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?

With no output schema, the description fully compensates by naming and explaining the relevant return fields, their interpretation, and the error-handling expectation. An agent has everything needed to call the tool and correctly relay its result.

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 coverage is 100% and the single parameter is fully documented in the schema. The description reinforces that the checked VAT number is DK plus the 8-digit CVR number but adds no format or syntactic detail beyond what the schema already provides, so the baseline 3 applies.

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: check whether DK plus a CVR number is a valid, active VAT number, and retrieve the register's name and address. It also distinguishes itself from every sibling by noting that VAT registration is not held in the CVR register and comes from a different source.

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?

Gives clear context for use when verifying a counterparty and comparing the VAT-register name with the CVR name, plus practical constraints: not in every plan and costs 1 credit. It does not explicitly name an alternative tool or state when not to use it, which keeps it from a 5.

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