Ärikratt

Observed corporate events

event_series

Read-only

Monthly observed legal-entity notice publications and registry relationships, separately. Notice counts are not unique insolvencies: notices are deduplicated across entities, but proceeding stages remain separate. Relationships count unordered company pairs by kind. Coverage and unmatched counts are national; older coverage is incomplete. County and sector filters use current classifications and overlap. Official Announcements attribution accompanies results. Old snapshots return empty rows; truncated results retain rows_total. Do not look up natural persons.

Input Schema

Name	Required	Description
`year`	No	Calendar year; defaults to snapshot year, which is partial.
`emtak`	No	Current snapshot Estonian Classification of Economic Activities (EMTAK) prefix, 1–5 digits.
`county`	No	Current snapshot county. Valid: Ida-Viru maakond, Lääne-Viru maakond, Harju maakond, Hiiu maakond, Jõgeva maakond, Järva maakond, Lääne maakond, Põlva maakond, Pärnu maakond, Rapla maakond, Saare maakond, Tartu maakond, Valga maakond, Viljandi maakond, Võru maakond, Maakond puudu.

Output Schema

Name	Required	Description
`note`	No
`rows`	Yes
`year`	No
`as_of`	Yes
`emtak`	No	Emtak. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.
`county`	No	County. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.
`reason`	No
`sources`	Yes
`truncated`	No
`data_as_of`	No	Event-series observation cutoff, separate from the snapshot publication clock.
`disclaimer`	Yes
`rows_total`	Yes
`first_month`	No	First month. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.
`snapshot_id`	Yes
`partial_year`	No
`invalid_dates`	No	Counts by event kind for invalid dates.
`coverage_basis`	No	Coverage basis. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.
`coverage_scope`	No	Coverage scope. event_series.event_series_payload: observed events and coverage, not unique insolvencies.
`future_notices`	No	Future notices. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.
`future_records`	No	Counts by event kind for future records.
`source_details`	Yes	Full attribution and acquisition evidence: source_metadata(key).
`kind_first_month`	No
`omitted_sections`	No	Sections removed to fit the response budget, including default sections. Request one named section to retrieve it. Present only when truncated.
`national_coverage`	No	National coverage. event_series.event_series_payload: observed events and coverage, not unique insolvencies.
`notices_available`	No	Notices available. event_series.event_series_payload: observed events and coverage, not unique insolvencies.
`notice_first_month`	No	Notice first month. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.
`invalid_date_notices`	No	Invalid date notices. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.
`relationship_first_month`	No	Relationship first month. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.
`excluded_relationships_without_two_company_joins`	No	Count of excluded company relationship pairs with a missing registry code or with one or both companies absent from the company join.

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedOct 29, 2026

addedOutput schema / properties / county

Added value: +{
+  "description": "County. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / coverage_basis

Added value: +{
+  "description": "Coverage basis. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / coverage_scope

Added value: +{
+  "description": "Coverage scope. event_series.event_series_payload: observed events and coverage, not unique insolvencies.",
+  "type": "string"
+}

addedOutput schema / properties / data_as_of

Added value: +{
+  "description": "Event-series observation cutoff, separate from the snapshot publication clock.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / emtak

Added value: +{
+  "description": "Emtak. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / excluded_relationships_without_two_company_joins

Added value: +{
+  "description": "Count of excluded company relationship pairs with a missing registry code or with one or both companies absent from the company join.",
+  "type": "integer"
+}

addedOutput schema / properties / first_month

Added value: +{
+  "description": "First month. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / future_notices

Added value: +{
+  "description": "Future notices. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.",
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / future_records

Added value: +{
+  "additionalProperties": {
+    "type": "integer"
+  },
+  "description": "Counts by event kind for future records.",
+  "type": "object"
+}

addedOutput schema / properties / invalid_date_notices

Added value: +{
+  "description": "Invalid date notices. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.",
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / invalid_dates

Added value: +{
+  "additionalProperties": {
+    "type": "integer"
+  },
+  "description": "Counts by event kind for invalid dates.",
+  "type": "object"
+}

addedOutput schema / properties / national_coverage

Added value: +{
+  "description": "National coverage. event_series.event_series_payload: observed events and coverage, not unique insolvencies.",
+  "type": "string"
+}

addedOutput schema / properties / notice_first_month

Added value: +{
+  "description": "Notice first month. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / notices_available

Added value: +{
+  "description": "Notices available. event_series.event_series_payload: observed events and coverage, not unique insolvencies.",
+  "type": "boolean"
+}

addedOutput schema / properties / relationship_first_month

Added value: +{
+  "description": "Relationship first month. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / rows / items / properties / matched_notices

Added value: +{
+  "description": "Matched notices. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.",
+  "type": [
+    "null",
+    "integer"
+  ]
+}

addedOutput schema / properties / rows / items / properties / partial

Added value: +{
+  "description": "Partial. event_series.event_series_payload: observed events and coverage, not unique insolvencies.",
+  "type": "boolean"
+}

addedOutput schema / properties / rows / items / properties / unmatched_notices

Added value: +{
+  "description": "Unmatched notices. event_series.event_series_payload: observed events and coverage, not unique insolvencies. Null when the source value or applicable observation is unavailable.",
+  "type": [
+    "null",
+    "integer"
+  ]
+}

addedOutput schema / properties / sources / items / properties / as_of_basis

Added value: +{
+  "description": "As of basis. event_series.event_series_payload: observed events and coverage, not unique insolvencies.",
+  "type": "string"
+}

Changed5 schema fields changedOct 18, 2026

addedOutput schema / properties / omitted_sections

Added value: +{
+  "description": "Sections removed to fit the response budget, including default sections. Request one named section to retrieve it. Present only when truncated.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / source_details

Added value: +{
+  "description": "Full attribution and acquisition evidence: source_metadata(key).",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / sources / items / properties / as_of
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
addedOutput schema / properties / sources / items / properties / key
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

changedOutput schema / required

Previous value: -[
-  "snapshot_id",
-  "as_of",
-  "sources",
-  "disclaimer",
-  "rows",
-  "rows_total"
-]New value: +[
+  "snapshot_id",
+  "as_of",
+  "sources",
+  "source_details",
+  "disclaimer",
+  "rows",
+  "rows_total"
+]

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / emtak / description

Previous value: -"Current snapshot EMTAK prefix, 1–5 digits."New value: +"Current snapshot Estonian Classification of Economic Activities (EMTAK) prefix, 1–5 digits."

Changed1 schema field changedOct 7, 2026

addedOutput schema / properties / kind_first_month

Added value: +{
+  "additionalProperties": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

AddedOct 5, 2026

TDQS

B3/5.0

Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses genuinely non-obvious behavior: notice counts are deduplicated across entities but proceeding stages stay separate, relationships count unordered pairs, coverage/unmatched counts are national and historically incomplete, old snapshots return empty rows, and truncated results retain rows_total. That is substantial operational context the annotations do not carry.

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?

Every sentence carries real information, but the text is telegraphic and run-on, with no front-loaded statement of what the tool does. A reader has to assemble the purpose from a chain of caveats, and 'separately' is left unexplained.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 shape needn't be spelled out, and the caveats around deduplication, coverage, and truncation are covered well. What remains missing is the basic framing — whether the result is a monthly series split by notice/relationship kind, and how the three filters interact to shape it.

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?

Schema coverage is 100%, so the schema already documents year, emtak, and county thoroughly, including the enum-like county list. The description adds only one semantic detail beyond the schema — that filters use current classifications and can overlap — which is useful but minor; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resources (monthly notice publications and registry relationships) but never states an action verb or what the tool actually returns — a monthly time series of two separate metrics. It does not differentiate itself from plausible siblings such as region_stats, sector_stats, or legal_calendar, so an agent must infer the distinction.

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

Usage Guidelines2/5

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

The only routing guidance is a negative exclusion ('Do not look up natural persons'). There is no statement of when to use this instead of region_stats or sector_stats, no prerequisite, and no mention of when a snapshot year versus an explicit year should be chosen.

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

All Ärikratt tools Inspect

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

Need Help?