Skip to main content
Glama

Hent virksomhed

hent_virksomhed
Read-onlyIdempotent

Stamdata for én virksomhed: navn, status, form, branche, by, stiftet, ansatte og hjemmeside. Eksempel: {"cvr": "10150817"} eller {"cvr": "10150817", "detaljer": "fuld"} (binavne, adresse, kontakt, de seneste 10 ændringer, Fødevarestyrelsens smiley-kontroller og vundne offentlige kontrakter (TED), hvis der er nogen, samt ansatte over tid med udviklingen det seneste år, aktive produktionsenheder og registreringshistorikken). Reklamebeskyttede virksomheder er markeret og må ikke bruges til markedsføring. Tæller 1 opslag. Kilde og dato står i svaret; nævn dem, når du bruger tallene.

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": "hent_virksomhed"
  }
}

Input Schema

NameRequiredDescriptionDefault
cvrYesCVR-nummer med 8 cifre, fx "10150817". Kender du kun navnet, så brug soeg_virksomhed først.
detaljerNo"kort" (standard) giver de vigtigste felter. "fuld" giver alle felter.kort

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive, and the description still adds substantive behavior: the call costs one lookup ("Tæller 1 opslag"), the response carries source and date that must be cited, and advertising-protected companies are flagged. It also discloses that optional datasets (TED contracts, food-inspection smileys) only appear when present, which prevents the agent from treating absence as an error.

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?

Purpose and field list are front-loaded, followed by the examples and then the caveats, so an agent gets the essentials in the first clause. The long nested parenthesis listing full-mode contents is dense and slightly hard to parse, but it is information-bearing rather than padding.

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?

There is no output schema, so the description must carry the return contract, and it does: field list for short mode, itemized contents for full mode, plus the note that source and date are in the response. Combined with the quota and marketing-restriction notes, nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented with type, enum and default, making 3 the baseline. The description goes beyond that by showing concrete example payloads for both modes and enumerating what the "fuld" enum value actually returns, which the schema only summarizes as "alle felter".

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?

"Stamdata for én virksomhed" plus an enumeration of the returned fields (navn, status, form, branche, by, stiftet, ansatte, hjemmeside) makes the verb, resource and scope unambiguous, and "én virksomhed" implicitly contrasts with the search/list siblings. It never names an actual sibling tool, so an agent must infer the boundary with soeg_virksomhed or fuld_rapport rather than being told it.

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 two example payloads show exactly how to call it in short vs. full mode, and the parenthetical spells out what "fuld" buys you, which is real selection guidance. It also states a when-not constraint ("Reklamebeskyttede virksomheder ... må ikke bruges til markedsføring"). What is missing is routing guidance against the many sibling tools that also return company data (hent_regnskab, fuld_rapport, kreditvurdering).

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