Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Czech company shareholders (public register, ISVR)

get_czech_company_shareholders
Read-only

Retrieve Czech company members and shareholders from the official public register, including contributions, shares, paid-up rates, and share capital for KYB checks.

Instructions

Members and shareholders of a Czech company from the official public register open data (ISVR, Ministry of Justice, daily snapshot): for an s.r.o., v.o.s. or k.s. every member with contribution, share (percentage or fraction as published) and paid-up rate; for an a.s. or SE the sole shareholder only (coverage says which); joint shares, released shares and share pledges counted; share capital. Legal persons are NAMED with their IČO (or foreign id and country); natural persons are COUNTED per role, never named (GDPR, rule R1), and an answer with natural persons only is still served and billed. A legal person's name covered by an objection (GDPR art. 21) is served as null and counted in ecartes.opposition; a company whose own name is covered returns the same 404 as an unknown IČO (not billed). Forms whose members the register does not publish, sole traders and undecided forms are refused 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": {
      "ico": "<ico>"
    },
    "name": "get_czech_company_shareholders"
  }
}

Input Schema

NameRequiredDescriptionDefault
icoYes8-digit Czech IČO of a LEGAL PERSON (leading zeros included), e.g. 27232433

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.3/5.0
Behavior5/5

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

Well beyond what readOnlyHint/openWorldHint convey: it discloses the GDPR rule that natural persons are counted per role and never named, that natural-persons-only answers are still served and billed, that an art. 21 objection yields null plus an entry in ecartes.opposition, which 404s are billed versus not billed, the $0.02 x402 payment, and the instruction to cite the returned `citation` verbatim. This is unusually rich behavioral disclosure for a paid, privacy-constrained read.

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?

Front-loaded with what it returns and roughly 120 words, with every clause carrying a constraint, a billing rule or a privacy rule. The semicolon-chained sentences and parentheticals make it dense to parse, but there is little true padding.

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?

Covers legal-form coverage, privacy handling, billing, error semantics and citation expectations; return values need not be spelled out because an output schema exists, yet the description still explains key output fields like coverage and ecartes.opposition. Nothing an agent needs to call this correctly and report the result is missing.

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 coverage is 100% and the schema already defines the single required parameter (8-digit IČO of a legal person), so the baseline would be 3. The description adds real selection meaning by tying the parameter to legal persons only and warning that sole traders and partially published forms produce a 404, which changes which identifiers an agent should submit.

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 and resource: members and shareholders of a Czech company from the ISVR open-data snapshot, and it scopes the answer by legal form (s.r.o./v.o.s./k.s. members with contribution, share and paid-up rate vs. a.s./SE sole shareholder). That specificity clearly separates it from an officers tool, but no sibling such as get_czech_company_officers is named, so an agent must infer the split from the wording alone.

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 explicit applicability boundaries and exclusions: sole traders, undecided forms and forms whose members the register does not publish are refused with a 404 that is not billed, and an unknown IČO returns the same 404. It never names an alternative tool to use instead for officers or for other jurisdictions, so routing is left to inference.

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