Sirenic

Danish company officers (CVR)

get_danish_company_officers

Read-only

Danish company officers and directors, live from CVR, the official Danish company registry (Erhvervsstyrelsen): executive board (Direktion), board of directors (Bestyrelse) with deputies and how each member was elected, fully liable partners of an I/S or K/S, and auditors — name, body, role and mandate dates. Active mandates by default; inclure_anciens adds ended mandates, which is where founders (stiftere) normally are. Long boards are capped at 300 active / 200 ended mandates, flagged by tronque (the counts stay exact). Beneficial owners (reelle ejere) are NOT exposed by this access and are never guessed. GDPR minimisation: no address, no personal identifier, and the register publishes no date of birth here. Paid via x402 ($0.01 in USDC or EURC).

Input Schema

TableJSON Schema

Name	Required	Description
`cvr`	Yes	8-digit Danish CVR number, e.g. 24256790
`api_key`	No	Optional Sirenic API key (srn_live_…) to pay with prepaid credits instead of x402 — no wallet needed. Get one at https://api.sirenic.eu/compte. Ignored when x_payment is provided (the signed payment wins). On insufficient balance the tool returns a credits error, not an x402 quote.
`x_payment`	No	Optional signed x402 PAYMENT-SIGNATURE header value. Omit to receive the payment quote.
`inclure_anciens`	No	Also return ended mandates, each with its end date

Output Schema

TableJSON Schema

Name	Required	Description
`hint`	No	How to settle the quote, present when payment_required is true.
`quote`	No	The signable x402 payment requirements when payment_required is true: {x402Version, accepts[]} where each entry carries scheme, network, amount, asset and payTo (USDC and EURC options at the same numeric amount). Sign one entry and call again with `x_payment`.
`resultat`	No	The endpoint's JSON response when payment_required is false. Paid responses carry `source`, `disclaimer` and an Ed25519 signature; KYB, batch KYB, sanctions, intelligence and the five invoicing tools (prepare_french_invoice_file, prepare_european_invoice_file, prepare_french_einvoicing_recipient, verify_iban_bank, validate_eu_vat_number) also carry a `provenance` array — one entry per block served, with the official register, licence, version, `as_of` date and `precision_as_of` (what that date means). Codes are documented at GET /v1/provenance/registres (free).
`payment_required`	Yes	True when this response is an x402 payment quote instead of data: settle one of the quote's `accepts` options and call the tool again with `x_payment`.

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds substantial behavioral context: default active-only results, truncation caps with the tronque flag, GDPR minimization, no guessing of beneficial owners, and x402 payment behavior. This goes well beyond what the annotations provide.

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?

Dense but well-organized: core purpose, mandate details, truncation limits, privacy exclusions, and cost each earn their place. Every sentence contributes useful operational or behavioral information without repetition or filler.

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?

Given that an output schema exists, the description does not need to explain return values. It covers the data source, default behavior, truncation behavior, exclusions, GDPR constraints, and payment mechanism, making the tool safely callable with minimal additional documentation.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful semantic context for inclure_anciens by noting that founders are usually found among ended mandates, and it clarifies the default filtering. It adds little beyond the schema for cvr, api_key, and x_payment, but those are already well-described.

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: retrieving Danish company officers and directors from the official CVR registry. It enumerates the exact officer categories (Direktion, Bestyrelse, I/S-K/S partners, auditors), making it clearly distinguishable from sibling country-officer tools.

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?

Provides clear routing guidance: Danish CVR is the source, active mandates are the default, inclure_anciens is needed for ended mandates/founders, and beneficial owners are explicitly NOT exposed by this access. That is an explicit when-not that tells an agent not to use this tool for beneficial-owner lookups.

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

All Sirenic tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation2/5

Several French company bundles overlap in purpose (get_french_company_file, get_french_company_kyb_file, get_french_company_intelligence, get_french_company_health_summary) and procurement/competitor tools overlap (get_french_company_public_procurement, get_eu_procurement_awards, get_company_procurement_competitors). Although descriptions try to differentiate, an agent could easily select the wrong tool when looking for a company overview or procurement history.

Naming Consistency4/5

Most tools follow a consistent get_/list_/search_ + country + entity pattern, e.g. get_french_company_profile, list_danish_company_filings, so navigation is predictable. Deviations like check_french_regulator_alerts, suggest_company_names, verify_iban_bank, and the prepare_* verbs are understandable but break the strict verb_noun pattern.

Tool Count1/5

77 tools is excessive for a single server regardless of how broad the domain is; the calibration treats 50+ as an extreme mismatch. While France is well covered and several countries appear, much of the surface is micro-endpoints (list_/get_ filing pairs per country) that could be consolidated.

Completeness3/5

France coverage is impressively complete (identity, financials, legal events, procurement, IP, risk, surveillance, invoicing), and the surveillance lifecycle has create/get/renew/stop. But European coverage is inconsistent: Germany has only insider transactions, Spain only acts, and several major jurisdictions lack accounts/officers/insolvency; an agent expecting 'European company due diligence' will hit dead ends.

Resources

Need Help?