Skip to main content
Glama

Nye virksomheder

nye_virksomheder
Read-onlyIdempotent

Nyregistrerede virksomheder, nyeste først, med filtre på branche, kommune, form og dato. Branche kan gives som tekst ("frisør", "tømrer") eller branchekode ("960210", "43"). En tekst bliver til én branchekode (den med flest virksomheder blandt træffene); svaret viser den i branche.brugt og de andre i branche.andre_muligheder. Fortæl altid brugeren, hvilken branchekode der blev brugt, og nævn alternativerne, så de kan vælge en anden. Eksempler: {"branche": "frisør", "kommune": "Aarhus"}, {"branchekode": "4322", "form": "ApS", "fra": "2026-11-01"}. "uden_hjemmeside": true kræver betalt pakke. Reklamebeskyttede virksomheder er filtreret fra. Tæller 1 opslag pr. kald.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nye_virksomheder"
  }
}

Input Schema

NameRequiredDescriptionDefault
fraNoStiftet fra og med denne dato, fx "2026-11-01".
tilNoStiftet til og med denne dato.
formNoVirksomhedsform, fx "ApS", "A/S" eller "Enkeltmandsvirksomhed".
efterNoNæste side: "naeste" fra forrige svar.
brancheNoBranche som tekst, fx "frisør".
graenseNoAntal (1-50, standard 20).
kommuneNoKommunens navn, fx "Aarhus" eller "København".
branchekodeNoBranchekode (DB07) eller begyndelsen af den, fx "4322" eller "43".
uden_hjemmesideNoKun virksomheder uden hjemmeside (kræver betalt pakke).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already establish this as a safe, idempotent, closed-world read, and the description still adds substantive behavior: ad-protected companies are silently filtered out, uden_hjemmeside requires a paid subscription, and each call costs one credit. It also discloses the non-obvious result behavior — that a text industry resolves to one code shown in branche.brugt with alternatives in branche.andre_muligheder — which no structured field conveys.

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?

The capability statement and filters are front-loaded, and the examples are compact and immediately usable. The instruction to always tell the user which code was used and to list alternatives is slightly repetitive with the preceding sentence, but it is actionable rather than padding.

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?

For a nine-parameter, zero-required tool with no output schema, the description covers the decisions an agent actually has to make: which industry parameter, what the response reveals, paid gating, credit cost and filtered-out records. Return structure is only partially characterized (only the branche fields are named), which is the main remaining gap.

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 the per-parameter baseline is 3, and the description earns above that by explaining the interaction between branche and branchekode (text collapses to a single code chosen by hit count) and by showing two concrete call examples. It does not explain the paging token beyond the schema's own wording, which keeps it from a 5.

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 opens with a precise verb+resource statement: newly registered companies, newest first, with filters on industry, municipality, legal form and date. That scope (only new registrations, sorted newest-first) is enough to distinguish it from the broader lookup siblings such as find_virksomheder or soeg_virksomhed without opening any schema.

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?

It gives clear context for use — filtering newly registered companies — and explicitly explains the choice between the two industry parameters (free text vs. DB07 code) plus the paid-package precondition for uden_hjemmeside. What it lacks is an explicit exclusion or hand-off, e.g. that existing-company lookups belong to a sibling tool, so an agent must infer that.

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