Skip to main content
Glama

run_dk_company_filings

Retrieve annual reports, announcements, and registrations for a Danish company (CVR). Returns dates, types, descriptions, and document links.

Instructions

Annual reports, announcements and registrations of one Danish company (CVR): date, type, description and document links. 1 point per returned record.

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": {
      "company": "<company>"
    },
    "name": "run_dk_company_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesRegistration number or registry URL. e.g. 24256790
max_itemsNoMax items (up to 250)
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the credit cost ('1 point per returned record') and implies a read-only listing of documents, but says nothing about pagination behavior, rate limits, or what happens when a company has no filings. The cost disclosure is real value, the rest of the behavioral profile is absent.

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?

Two tight sentences with no filler, front-loaded with the resource and scope before the record fields and cost. Every clause carries information, though the field list and cost could be ordered slightly more usefully.

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 does the necessary work by enumerating the returned record fields (date, type, description, document links). For a 3-parameter, single-output tool this is nearly sufficient; missing pagination guidance for start_page/max_items is the only meaningful gap.

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 description coverage is 100%, so company, max_items and start_page are already documented in the schema; the baseline of 3 applies. The description's field list ('date, type, description and document links') describes the return payload rather than the inputs, so it adds nothing new about parameters.

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 a specific resource and scope: annual reports, announcements and registrations for one Danish company identified by CVR, plus the record fields returned. 'Of one Danish company' distinguishes it from the sibling run_dk_companies_search, though it never names that sibling explicitly, so differentiation is implicit rather than stated.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no alternative named. The phrase 'of one Danish company (CVR)' hints that a registration number is required input, but nothing tells the agent how to obtain a CVR or when filings are preferable to run_dk_companies / run_dk_companies_search.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools