Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Estonian company members and shareholders

get_estonian_company_shareholders
Read-only

Retrieve an Estonian company's shareholders and members from the official e-Business Register, including holding percentages, ownership type, and registration details for legal-person due diligence.

Instructions

Members and shareholders of an Estonian company from the official e-Business Register share register (RIK, CC BY 4.0), refreshed daily from the national photo: holding percentage, nominal value and currency as published (EEK before 2011, never converted), ownership type (sole, joint, undivided), verification source and registration date; AS shareholders and founders recorded beside the card under the same rule; share pledges and conditional transfers; capital from the general data when fresh; detenu_par_personnes_physiques_pct. Corporate holders are named with their registrikood or foreign code and country; natural persons are COUNTED with their holding and never named (GDPR, no chain to natural persons). Legal persons only: sole proprietorships are refused (404, payment cancelled), as is a legal person known only from the monthly identity copy, not covered by the daily photo (404 mandats_non_couverts). aucun_associe_inscrit: true is a register fact for a known legal person (its meaning depends on the legal form: dematerialised AS shares are held by the central depository). Paid via x402 ($0.02 in USDC or EURC). When you report a result, cite its citation verbatim.

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": {
      "registrikood": "<registrikood>"
    },
    "name": "get_estonian_company_shareholders"
  }
}

Input Schema

NameRequiredDescriptionDefault
registrikoodYes8-digit Estonian registry code (registrikood, e-Business Register), e.g. 10003666

Output Schema

NameRequiredDescriptionDefault
hintNoHow to settle the quote, present when payment_required is true.
quoteNoThe 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`.
resultatNoThe endpoint's JSON response when payment_required is false. Paid responses carry `source`, `disclaimer` and an Ed25519 signature, and every paid JSON response carries a `provenance` array (all tools since 2026-09-06): one entry per block served, with the official register, licence, version, `empreinte_sha256` (full snapshots), `as_of` date and `precision_as_of` (what that date means), plus the common per-block envelope: `etat` in a closed list (servi, absence_mesuree, absence_non_conclusive, partiel, perime, indisponible, sans_objet), `motif` when unavailable, `age_jours` (only for publication or ingestion dates), `couverture` (complete / partielle / non_mesurable with its measure) and `confiance` in bands (faible / moyenne / forte, only where a measure grounds it, never averaged across blocks). Read the states before the numbers: an absence_non_conclusive, indisponible or partiel block is never « nothing to report »; only absence_mesuree asserts an absence. Register codes: GET /v1/provenance/registres ; states, closed lists and reading rules: GET /v1/lecture (both free). The PDF tools carry no JSON envelope (the PDF report prints it).
free_tierNoFree API key offer for this tool, present with a quote.
payment_requiredYesTrue 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`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Despite annotations covering read-only and open-world behavior, the description adds substantial context an agent could not infer: daily refresh from the national photo, EEK-denominated values never converted, GDPR-driven counting (not naming) of natural persons, two distinct 404 conditions with named codes, and the specific response state aucun_associe_inscrit. It also discloses payment via x402 at $0.02 and the citation obligation.

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

Conciseness3/5

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

The scope is front-loaded in the first clause, but the remainder is one sprawling run-on packed with semicolons and untranslated internal field names (detenu_par_personnes_physiques_pct, mandats_non_couverts, aucun_associe_inscrit) that are hard to parse. Most content is substantive, but the mixing of English and French identifiers and the lack of sentence breaks hurt scannability.

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?

With an output schema present, return values need not be explained, and the description still covers data provenance, licensing, refresh, currency handling, exclusion cases, response flags, and pricing. An agent has everything needed to decide whether to call it and how to interpret a 404.

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?

There is a single required parameter at 100% schema coverage, and the schema already specifies the 8-digit registrikood pattern with an example. The description adds no format or validity detail beyond the schema, so the baseline of 3 applies.

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?

The opening clause names a specific verb and resource: members and shareholders of an Estonian company from the official e-Business Register share register, with the data source and refresh cadence identified. It is clearly distinct from sibling tools like get_estonian_company_officers or get_estonian_company_accounts by resource, though it never explicitly states that differentiation.

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?

Usage boundaries are stated concretely: legal persons only, sole proprietorships refused, and legal persons known only from the monthly identity copy refused. What is missing is any explicit routing advice versus adjacent tools (officers, general registry data) when an agent is unsure which resource holds a given fact.

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