Skip to main content
Glama

Sammenlign virksomheder

sammenlign_virksomheder
Read-onlyIdempotent

Nøgletal for 2 til 5 virksomheder side om side: seneste regnskab (omsætning, resultat, egenkapital, balance, ansatte) og kreditscore. Eksempel: {"cvr": ["10150817", "12345678"]}. Kender du ikke konkurrenterne, så spørg brugeren, hvem de er (eller hvilke CVR-numre), i stedet for at gætte dem. Kræver betalt pakke. Tæller 1 opslag pr. virksomhed.

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

Input Schema

NameRequiredDescriptionDefault
cvrYes2 til 5 forskellige CVR-numre.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds two genuinely useful facts beyond them: a paid subscription is required and each company counts as one lookup (quota impact). It does not address what happens with invalid or duplicate CVR numbers.

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

Conciseness5/5

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

Four short sentences, front-loaded with the return payload, followed by the example, the anti-guessing rule, and cost. Every sentence carries distinct information with no repetition.

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?

With no output schema, the description correctly compensates by enumerating the returned metrics, and it covers cost and access requirements. Minor gap: no statement on error handling for malformed CVRs or how results are ordered.

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% and already documents the 2-5 item array and CVR format, so the baseline is 3. The inline JSON example and the note that billing is per company add meaning about how the array is consumed, pushing it slightly above baseline.

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?

States precisely what the tool returns for a bounded set of entities: key figures for 2-5 companies side by side, enumerating the metrics (revenue, profit, equity, balance, employees) plus credit score. The multi-company scope implicitly separates it from single-company siblings like hent_virksomhed, but no alternative is named explicitly.

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 usage context (comparison of 2-5 companies) and an explicit behavioral instruction: if you don't know the competitors, ask the user rather than guessing. It also notes the paid-package prerequisite and per-company lookup cost, but never names the fallback tool for name-only lookups or single-company requests.

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