Skip to main content
Glama

Sirenic

by eu.sirenic
OverviewDiscussionsAdmin

Latvian company members and shareholders

get_latvian_company_shareholders
Read-only

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 are COUNTED, never named (GDPR); dematerialised shares show the depository only. Group links for KYB.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regnrYes11-digit Latvian registration number (Uzņēmumu reģistrs), e.g. 40003032065
api_keyNoOptional 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_paymentNoOptional signed x402 PAYMENT-SIGNATURE header value. Omit to receive the payment quote.

Output Schema

TableJSON 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, `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).
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. Added

TDQS

A4.3/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the readOnlyHint: natural persons are only counted and never named due to GDPR, corporate holders appear with registration numbers, and dematerialised shares show only the depository. It also notes the official CC0 daily source. No contradiction with annotations.

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?

The description is dense but entirely relevant: it covers the resource, jurisdiction, data source, returned fields, privacy constraints, and KYB linkage in two sentences. Nothing is repetitive or wasted, and the core purpose is front-loaded.

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?

The tool has an output schema, read-only/open-world annotations, and a fully documented parameter schema. The description covers source quality (CC0, daily), content granularity, privacy behavior, and KYB group links. There is no meaningful missing context for an agent to call this tool correctly.

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?

The schema already covers all three parameters with descriptions at 100% coverage, so the description does not need to explain regnr, api_key, or x_payment. The description contributes nothing about parameter usage, but does not need to since schema coverage is complete. Baseline 3 is appropriate.

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?

The description states a specific resource ('Latvian company members (SIA) and registered shareholders (AS)') with a clear data source and jurisdiction. It lists the exact data fields returned (shares, nominal value, votes, holding start date, etc.), which distinguishes it from sibling tools like get_latvian_company_officers or get_latvian_company_beneficial_owners.

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

Usage Guidelines3/5

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

The implied usage is clear: call this tool when you need shareholder/member data for Latvian companies. However, the description gives no explicit when-to-use guidance, no exclusions, and does not name any alternative tools or scenarios where a sibling would be more appropriate.

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

All Sirenic toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources