Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Latvian company members and shareholders

get_latvian_company_shareholders
Read-only

Retrieve Latvian company members or registered shareholders from official registry data, including share counts, nominal value, votes, capital share, and holding start dates for KYB checks.

Instructions

Latvian company members (SIA) and registered shareholders (AS) from the official Uzņēmumu reģistrs open data (CC0, daily): number of shares, nominal value and currency as published, votes, share of nominal capital, holding start date. Corporate holders are named with their registration number; natural persons, individual merchants included, are COUNTED, never named (GDPR); dematerialised shares show the depository only. Group links for KYB. The answer carries the company's statut and statut_detail: an active company with none gets aucun_associe_inscrit: true; a struck-off company whose records the register removed returns 404 radiee_inscriptions_retirees, not billed; one that keeps some is served under partial coverage. Legal persons only: an individual merchant (IK), a sole trader or a form not recognised as a legal person returns 404, not billed. 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": {
      "regnr": "<regnr>"
    },
    "name": "get_latvian_company_shareholders"
  }
}

Input Schema

NameRequiredDescriptionDefault
regnrYes11-digit Latvian registration number (Uzņēmumu reģistrs), e.g. 40003032065

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?

Annotations only say readOnly and openWorld, so the description carries real weight and delivers: GDPR-driven counting (never naming) of natural persons, depository-only display for dematerialised shares, partial-coverage states, not-billed 404 paths with their specific codes, and a paid x402 call at $0.02 in USDC or EURC. An agent knows the safety profile, the cost, the failure modes, and the redaction behaviour before invoking it.

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 content is front-loaded usefully — data source and fields first, then edge cases — but it is delivered as one long, comma-spliced run of facts mixing English with untranslated tokens (aucun_associe_inscrit, radiee_inscriptions_retirees, statut/statut_detail). Nothing is clearly wasted, yet the density and lack of sentence breaks make it harder to parse than it needs to be.

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?

An output schema exists, so return values need not be re-explained, and the description still covers the things structure cannot: cost, billing exemptions, error semantics, coverage caveats, GDPR limits, and the instruction to cite the citation verbatim. For a single-parameter lookup with a rich response, nothing an agent needs is missing.

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 parameter and schema coverage is 100%, with a pattern and a worked example (40003032065) already in the schema. The description adds no format, normalisation, or lookup guidance beyond that, so the baseline of 3 is correct.

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 verb+resource combination: Latvian company members (SIA) and registered shareholders (AS), with the data source (Uzņēmumu reģistrs) and the exact fields returned (shares, nominal value, votes, share of nominal capital, holding start date). That is enough to separate it from neighbouring tools such as get_latvian_company_officers or get_latvian_company_accounts, though it never names an alternative explicitly, which keeps it just short of a 5.

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 applicability rules: legal persons only, so an individual merchant (IK), sole trader, or unrecognised form returns 404; struck-off companies whose records were removed return 404; an active company with no recorded members gets aucun_associe_inscrit: true. It also signals the KYB group-link use case. What it lacks is an explicit 'use X instead' routing to the sibling officers or accounts tools.

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