Skip to main content
Glama

Sirenic

by eu.sirenic
OverviewDiscussionsAdmin

Croatian company insolvency (Sudski registar)

get_croatian_company_insolvency
Read-only

Croatian company insolvency status from the official Sudski registar (court register, daily snapshot of the open API, Otvorena dozvola): running procedure — bankruptcy (stečaj), liquidation, pre-bankruptcy stages, bankruptcy or liquidation estate — and every published court decision with its extracted facts (court, case reference, date), never the decision text. aucune_procedure: true is a measured fact on the complete snapshot. Unknown OIB/MBS = 404 (deleted subjects are not published by the API). Paid via x402 ($0.02 in USDC or EURC).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
oibYes11-digit Croatian OIB (e.g. 92803032010); an 8- or 9-digit MBS court-register number is accepted too
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.4/5.0
Behavior5/5

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

Beyond readOnly/openWorld annotations, the description reveals important behavior: it never returns decision text, `aucune_procedure: true` is a measured fact on the complete snapshot, unknown identifiers produce 404 because deleted subjects are unpublished, and the call is paid via x402. This is substantive, non-obvious behavioral context that helps the agent interpret results correctly.

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?

The essential purpose is front-loaded, and the extra clauses about source, output scope, the no-procedure flag, 404 semantics, and pricing are each informative. The long first sentence is dense but not wasteful; a small structural cleanup would make it very strong.

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?

For a read-only, paid, country-specific insolvency lookup, the description covers data source, output content limitations, key flag semantics, error behavior for unknown identifiers, and cost. With the output schema and annotations also available, nothing an agent needs to call and interpret this tool 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?

The input schema already describes all three parameters with 100% coverage, so the baseline applies. The description reinforces that OIB/MBS strings are valid and mentions payment-related handling, but it does not add material meaning beyond the schema.

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 names a specific verb and resource — retrieving Croatian insolvency status from the official Sudski registar — and enumerates the covered procedures and court decisions. This scope clearly differentiates it from country-specific siblings such as get_croatian_company_accounts/events and other countries' insolvency tools.

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?

The Croatian court-register subject matter gives clear context for when this tool is appropriate, and the 404/unknown-OIB behavior plus payment requirement set expectations. It does not explicitly name alternative siblings or state 'when not to use', but the country/data-source framing makes the intended use obvious.

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