Skip to main content
Glama

Søg virksomhed

soeg_virksomhed
Read-onlyIdempotent

Find danske virksomheder i CVR på navn, CVR-nummer, domæne eller mail. Brug det først, når du kun kender navnet. Eksempler: {"tekst": "Mahoje"}, {"tekst": "mahoje.dk"}, {"tekst": "info@firma.dk"}, {"tekst": "10150817"}. Svaret er en liste med cvr, navn, by og status, aktive virksomheder før ophørte; brug cvr i de andre værktøjer. Ved flere træf: vælg det aktive selskab, der passer bedst, og sig til brugeren, hvilket du valgte; passer flere aktive lige godt, så spørg brugeren. Til lister med filtre (branche, sted, størrelse) bruger du find_virksomheder. Tæller 1 opslag.

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": {
      "tekst": "<tekst>"
    },
    "name": "soeg_virksomhed"
  }
}

Input Schema

NameRequiredDescriptionDefault
tekstYesNavn, CVR-nummer, domæne eller mail. Mindst 2 tegn.
graenseNoHøjst så mange træf (1-25, standard 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses the response shape (list of cvr, navn, by, status), ordering (active companies before ceased ones), and cost ('Tæller 1 opslag'), and it tells the agent to reuse the returned cvr in other tools. It does not cover empty-result or error behavior, which keeps it short of a 5.

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?

It is front-loaded with purpose, then usage, then examples, then follow-up routing, so the agent hits the decisive information first. It is dense but nearly every clause carries operational value; only the example list is slightly redundant with the schema.

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?

For a two-parameter read-only lookup with full annotation coverage and no output schema, the description supplies everything an agent needs: when to use it, what the return list contains, how to handle ambiguity, and which tool to use for filtered lists.

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 schema already defines 'tekst' as name, CVR number, domain or mail. The four examples illustrate concrete input formats but essentially restate what the schema says, and the graense parameter is never mentioned, so the description adds little meaning beyond the schema.

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 names a specific verb and resource in Danish CVR ('Find danske virksomheder i CVR') and enumerates the matching keys (navn, CVR-nummer, domæne, mail). It also explicitly contrasts itself with the sibling find_virksomheder, so an agent can distinguish name-lookup from filtered listing without opening either schema.

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

Usage Guidelines5/5

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

'Brug det først, når du kun kender navnet' states the triggering condition, and 'Til lister med filtre (branche, sted, størrelse) bruger du find_virksomheder' names the alternative plus the condition selecting it. The multi-hit branch also prescribes behavior: prefer the active company, tell the user which one was chosen, and ask if several active ones fit equally well.

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