Skip to main content
Glama

Overvåg virksomhed

overvaag_virksomhed
Destructive

Følg en virksomhed og få besked ved hændelser (konkurs, ny direktør, adresse, nyt regnskab …). Beskeden leveres enten som webhook (JSON til en https-adresse, hvis webhook_url er sat) eller som én samlet daglig mail; der findes ingen andre kanaler (ingen SMS, Slack, push eller øjeblikkelig mail). handling: "foelg" (kræver cvr), "stop" (kræver cvr) eller "liste". Eksempler: {"handling": "foelg", "cvr": "10150817"}, {"handling": "foelg", "cvr": "10150817", "webhook_url": "https://example.com/hook"}, {"handling": "liste"}. Spørg brugeren, før du følger eller stopper. Kræver betalt pakke. Tæller ikke 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": {
      "handling": "<handling>"
    },
    "name": "overvaag_virksomhed"
  }
}

Input Schema

NameRequiredDescriptionDefault
cvrNoCVR-nummer med 8 cifre, fx "10150817". Kender du kun navnet, så brug soeg_virksomhed først.
emailNoSamlet mail om dagen (standard: ja, hvis der ikke er en webhook).
handlingYes"foelg", "stop" eller "liste".
webhook_urlNohttps-adresse, der skal have hændelser som JSON.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description adds substantive context beyond them: only two delivery channels exist (webhook JSON to an https URL, or one consolidated daily email), with SMS, Slack, push and instant mail explicitly ruled out. It also discloses the paid-package prerequisite and the confirmation requirement before follow/stop. It does not say what happens when following an already-followed company, relevant since idempotentHint=false.

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 purpose, then channels, then the handling values, then examples — a sensible order with no filler sentences. The three inline JSON examples are dense but each demonstrates a distinct mode, so they earn their space.

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 mutation tool with no output schema, it covers channels, prerequisites, confirmation behavior and invocation examples. What 'liste' returns and the effect of re-following a company are left implicit, a minor gap given the otherwise thorough coverage.

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 baseline is 3, but the description adds meaning the schema lacks: cvr is required for 'foelg' and 'stop', webhook takes precedence when webhook_url is set, and three worked examples show valid parameter combinations. This conditional dependency between handling and cvr is not expressed in the schema itself.

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 ('Følg en virksomhed og få besked ved hændelser') and enumerates the event types (konkurs, ny direktør, adresse, nyt regnskab). The three handling values (foelg/stop/liste) make the operational scope unambiguous, so an agent can tell this apart from the read-only lookup siblings.

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 concrete operating conditions: ask the user before following or stopping, requires a paid package, and does not count against lookup quota. It does not name an alternative sibling, but the schema's cvr field points to soeg_virksomhed for name-to-CVR resolution, which covers the main routing decision.

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