Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Slovak annual accounts (RUZ)

get_slovak_company_filing
Read-only

Retrieves a Slovak company's balance sheet and profit and loss data from RÚZ filings for a given fiscal year, with 16 key euro items and prior-year comparatives.

Instructions

One Slovak fiscal year decoded from the structured statements filed with the RÚZ: balance sheet and profit and loss, 16 key items: net turnover (null = not published, never zero), operating income and costs, value added, staff costs, operating, financial, pre-tax and net result, income tax, total assets, non-current and current assets, equity, share capital, liabilities, plus prior-year comparatives as published in the same filing. Amounts in euros, never converted. Closing date comes from list_slovak_company_filings; scope defaults to the statutory filing. A unit whose legal form is not a served legal person's returns 404, not billed. Paid via x402 ($0.03 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>",
      "date_cloture": "<date_cloture>"
    },
    "name": "get_slovak_company_filing"
  }
}

Input Schema

NameRequiredDescriptionDefault
icoYes8-digit Slovak IČO, e.g. 36417475
perimetreNoFiling scope: statutory (default) or consolidated, never merged
type_depotNoFiling type from the filings list (Riadna, Mimoriadna…), when two filings share the same closing date; defaults to the ordinary one
date_clotureYesFiscal-year closing date, YYYY-MM-DD, e.g. 2025-12-31

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

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

Adds substantial behavior beyond the readOnly/openWorld annotations: null means not published (never zero), amounts are in euros and never converted, unserved legal forms return 404 and are not billed, and the call is paid via x402 at $0.03. It also instructs citing the `citation` verbatim, which is real operational context.

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-loads the core purpose and item list, then layers constraints and billing. It is dense but nearly every clause carries information; the long enumeration of 16 items is the only mildly heavy part, though it is useful for selection.

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?

Given an output schema exists, the description needn't explain return structure, yet it still summarizes the returned items and comparatives. Combined with billing, error, and citation guidance, an agent has everything needed to call it correctly.

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%, so the baseline is 3, but the description adds meaning: it clarifies the closing date's provenance, that scope defaults to statutory and is never merged, and that type_depot defaults to the ordinary filing. This goes beyond the schema's own field descriptions.

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?

States a specific verb and resource ('One Slovak fiscal year decoded from the structured statements filed with the RÚZ') and enumerates the 16 line items returned, so an agent knows exactly what data it gets. It also implicitly separates itself from list_slovak_company_filings by noting the closing date comes from that tool.

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 concrete prerequisites and defaults: closing date must come from list_slovak_company_filings, scope defaults to statutory, and type_depot is used when two filings share a closing date. It stops short of explicit when-not-to-use guidance or naming a consolidated alternative beyond the perimetre enum.

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