Estonian court decisions: full-text case-law search, each ruling linked to its companies. Free.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Given a ruling id, return documents from Estonian public-authority document registers that name the same companies - procurement files, licences, correspondence, inspections. A court dispute and an authority's file about the same company are the two halves nobody normally sees together. Sourced from dokumendiregister.ee. This depends on the ruling having a company linked to it, which holds for about 19% of the corpus: parties are extracted from the decision text by registry code, and a judgment that names a company without its code yields no link. An empty list therefore means either no linked company or no matching documents - it is not evidence that no authority holds a file.
Ruling id, e.g. 'ruling:1279503'.
Max documents (default 8).
Given a ruling id, return documents from Estonian public-authority document registers that name the same companies - procurement files, licences, correspondence, inspections. A court dispute and an authority's file about the same company are the two halves nobody normally sees together. Sourced from dokumendiregister.ee. This depends on the ruling having a company linked to it, which holds for about 19% of the corpus: parties are extracted from the decision text by registry code, and a judgment that names a company without its code yields no link. An empty list therefore means either no linked company or no matching documents - it is not evidence that no authority holds a file.
| Argument | Type | Description |
|---|---|---|
| id* | string | Ruling id, e.g. 'ruling:1279503'. |
| limit | integer | Max documents (default 8). |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Ruling id, e.g. 'ruling:1279503'."
},
"limit": {
"type": "integer",
"maximum": 25,
"minimum": 1,
"description": "Max documents (default 8)."
}
},
"additionalProperties": false
}Given a CELEX (an act like '32016R0679', or a Court of Justice judgment like '62014CJ0362'), return the Estonian court decisions that cite it. This is the join no other source publishes: EUR-Lex knows the EU instrument, Riigi Teataja knows the Estonian decision, and nobody connects them.
| Argument | Type | Description |
|---|---|---|
| celex* | string | CELEX of an EU act or judgment. |
| limit | integer | |
| article | string | Only decisions citing this article of the act. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"celex"
],
"properties": {
"celex": {
"type": "string",
"description": "CELEX of an EU act or judgment."
},
"limit": {
"type": "integer",
"maximum": 50,
"minimum": 1
},
"article": {
"type": "string",
"description": "Only decisions citing this article of the act."
}
},
"additionalProperties": false
}Fetch an EU regulation or directive by CELEX (e.g. '32016R0679' for the GDPR), article by article, in Estonian. Also reports how many Estonian court decisions cite it and which articles they lean on - the part EUR-Lex cannot answer.
| Argument | Type | Description |
|---|---|---|
| celex* | string | CELEX number, e.g. '32016R0679'. Sector 3 acts only. |
| article | string | Return only this article, e.g. '5'. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"celex"
],
"properties": {
"celex": {
"type": "string",
"description": "CELEX number, e.g. '32016R0679'. Sector 3 acts only."
},
"article": {
"type": "string",
"description": "Return only this article, e.g. '5'."
}
},
"additionalProperties": false
}Given an Estonian ruling id (from `search`), list the EU instruments it cites - regulations, directives and Court of Justice judgments - with the articles named where the decision names them.
| Argument | Type | Description |
|---|---|---|
| id* | string | Ruling id, e.g. 'ruling:1279503'. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Ruling id, e.g. 'ruling:1279503'."
}
},
"additionalProperties": false
}Search EU regulations and directives, and Court of Justice / European Court of Human Rights judgments, by Estonian title or case number. The corpus is Estonian-language throughout: 94% of the Court of Justice's output is translated into Estonian, and essentially nothing indexes it in Estonian. Returns ids usable with eu_law_fetch.
| Argument | Type | Description |
|---|---|---|
| limit | integer | |
| query* | string | Estonian title words, or a case number such as 'C-362/14'. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 30,
"minimum": 1
},
"query": {
"type": "string",
"description": "Estonian title words, or a case number such as 'C-362/14'."
}
},
"additionalProperties": false
}Retrieve the full text + metadata for any `id` returned by `search`. Handles all three kinds: `ruling:<n>` (a court decision with its linked companies), `law:<n>` (an act in its current redaktsioon, all paragraphs) and `section:<n>:<par>` (a single paragraph - prefer this over pulling a whole act). Returns Markdown plus the canonical lahend.ee URL.
| Argument | Type | Description |
|---|---|---|
| id* | string | Typed id from `search`: 'ruling:1279503', 'law:12345' or 'section:12345:199'. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Typed id from `search`: 'ruling:1279503', 'law:12345' or 'section:12345:199'."
}
},
"additionalProperties": false
}Return a single § of an Estonian act, addressed the way lawyers cite it: an abbreviation and a number, e.g. abbrev='KarS', paragrahv='199', or abbrev='TsMS', paragrahv='430'. This is the precise way to answer a legal question - pulling a whole act costs thousands of tokens and buries the answer. Text comes from the act's current redaktsioon.
| Argument | Type | Description |
|---|---|---|
| abbrev* | string | Act abbreviation as cited: KarS, TsMS, VÕS, PankrS, RahaPTS… |
| paragrahv* | string | Paragraph number, e.g. '199'. Superscript sections are addressed as '43-1' or '43¹' (§ 43¹) - these are DIFFERENT provisions from § 43. A full citation like '§ 430 lg 1' is also accepted; the lõige is ignored. A bare second number ('43 1') is rejected as ambiguous rather than silently read as § 43. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"abbrev",
"paragrahv"
],
"properties": {
"abbrev": {
"type": "string",
"description": "Act abbreviation as cited: KarS, TsMS, VÕS, PankrS, RahaPTS…"
},
"paragrahv": {
"type": "string",
"description": "Paragraph number, e.g. '199'. Superscript sections are addressed as '43-1' or '43¹' (§ 43¹) - these are DIFFERENT provisions from § 43. A full citation like '§ 430 lg 1' is also accepted; the lõige is ignored. A bare second number ('43 1') is rejected as ambiguous rather than silently read as § 43."
}
},
"additionalProperties": false
}List an act's redaktsioonid (consolidated versions) with their validity ranges, newest first. Use this to answer 'what did this say on date X' - Estonian law is amended constantly and the current text is often not the one that applied to the facts.
| Argument | Type | Description |
|---|---|---|
| abbrev* | string | Act abbreviation, e.g. 'TsMS'. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"abbrev"
],
"properties": {
"abbrev": {
"type": "string",
"description": "Act abbreviation, e.g. 'TsMS'."
}
},
"additionalProperties": false
}All areas of law (asja_kategooria) present in the corpus, each with its ruling count. Use a category as the `category` filter in `search_rulings`. These counts do NOT sum to the corpus size: about 26% of rulings carry no category, so they appear in `list_courts` totals and in unfiltered search but in no category here. Filtering by category silently excludes them.
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}All Estonian courts that have published decisions, each with its ruling count. Use a court name as the `court` filter in `search_rulings`.
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}Ranked by how many Estonian decisions cite them. A good starting point for 'which EU law actually matters in Estonian practice' - the answer is concentrated in consumer protection, jurisdiction, asylum and agriculture rather than spread evenly.
| Argument | Type | Description |
|---|---|---|
| limit | integer |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "integer",
"maximum": 50,
"minimum": 1
}
},
"additionalProperties": false
}The statute paragraphs cited by the most court decisions, ranked. A map of where Estonian litigation actually happens, and a good starting point when exploring an unfamiliar area.
| Argument | Type | Description |
|---|---|---|
| limit | integer | How many (default 20). |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "integer",
"maximum": 50,
"minimum": 1,
"description": "How many (default 20)."
}
},
"additionalProperties": false
}The newest published rulings (by decision date), across all courts and areas of law.
| Argument | Type | Description |
|---|---|---|
| limit | integer |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "integer",
"maximum": 25,
"minimum": 1
}
},
"additionalProperties": false
}Given an 8-digit Estonian registry code (registrikood), return every court decision that names that company, with its role (claimant/defendant/etc.) and the other parties. This company↔case-law join is unique to lahend.ee. Find a registry code via nimistu.ee or the nimistu MCP.
| Argument | Type | Description |
|---|---|---|
| limit | integer | |
| reg_code* | string | 8-digit Estonian company registry code, e.g. '16887028'. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"reg_code"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 50,
"minimum": 1
},
"reg_code": {
"type": "string",
"description": "8-digit Estonian company registry code, e.g. '16887028'."
}
},
"additionalProperties": false
}Given an act abbreviation and a §, return the court decisions that actually cite it, newest first, with a total count. Built from 3.05M citations extracted from the decision texts themselves. This answers 'how have the courts applied KarS § 199' - the question statute text alone cannot answer, and the reason to use lahend.ee over reading Riigi Teataja.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Max rulings returned (default 10). |
| abbrev* | string | Act abbreviation as cited: KarS, TsMS, VÕS, PankrS… |
| paragrahv* | string | Paragraph number, e.g. '199'. A full citation is accepted; the lõige is ignored. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"abbrev",
"paragrahv"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 25,
"minimum": 1,
"description": "Max rulings returned (default 10)."
},
"abbrev": {
"type": "string",
"description": "Act abbreviation as cited: KarS, TsMS, VÕS, PankrS…"
},
"paragrahv": {
"type": "string",
"description": "Paragraph number, e.g. '199'. A full citation is accepted; the lõige is ignored."
}
},
"additionalProperties": false
}Full-text search across Estonian LAW - both court decisions (civil, administrative and criminal rulings) and legislation (acts and their individual paragraphs), from Riigi Teataja, indexed by lahend.ee. Inflection-tolerant; wrap a phrase in "quotes" for an exact match. Every result carries a stable typed `id` - `ruling:<n>`, `law:<n>` or `section:<n>:<par>` - which `fetch` resolves. Use this when you need the legal position on something and do not yet know whether the answer is in a statute or in case law.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Max results (default 10). |
| query* | string | Legal terms, a case number, a party/company name, or a "quoted phrase". |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 25,
"minimum": 1,
"description": "Max results (default 10)."
},
"query": {
"type": "string",
"description": "Legal terms, a case number, a party/company name, or a \"quoted phrase\"."
}
},
"additionalProperties": false
}Full-text search across the paragraphs of every in-force Estonian act (4M+ sections). Answers 'which provision governs X' directly, returning the paragraphs themselves rather than acts you then have to read. Each hit carries a `section:` id for `fetch`.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Max results (default 8). |
| query* | string | A legal term or phrase, e.g. 'pankrotiavaldus', 'ehitusluba', 'töölepingu ülesütlemine'. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 25,
"minimum": 1,
"description": "Max results (default 8)."
},
"query": {
"type": "string",
"description": "A legal term or phrase, e.g. 'pankrotiavaldus', 'ehitusluba', 'töölepingu ülesütlemine'."
}
},
"additionalProperties": false
}Find Estonian acts by title or abbreviation (KarS, TsMS, VÕS…). Returns each act with a `law:` id for `fetch`, its type, issuer and whether it is still in force. Use get_law_section when you already know the paragraph you want.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Max results (default 10). |
| query* | string | Title fragment or abbreviation. |
| inForceOnly | boolean | Only acts currently in force (default true). |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 25,
"minimum": 1,
"description": "Max results (default 10)."
},
"query": {
"type": "string",
"description": "Title fragment or abbreviation."
},
"inForceOnly": {
"type": "boolean",
"description": "Only acts currently in force (default true)."
}
},
"additionalProperties": false
}Full-text ruling search with optional filters: court name, case type (civil/administrative/criminal), area of law (asja_kategooria) and a decision-date range. Returns a page of rulings with a total count. Use `list_courts` / `list_categories` to discover valid filter values. Two coverage limits worth knowing, because both are silent: - `companies` is populated on about 19% of rulings. Parties are extracted from the decision text by registry code, and many judgments name a company without ever stating its code. An EMPTY array means no code was found in the text, NOT that no company was involved. - About 26% of rulings carry no `asja_kategooria` at all, so filtering by `category` silently excludes them. Omit the filter to search the whole corpus.
| Argument | Type | Description |
|---|---|---|
| court | string | Exact court name, e.g. 'Harju Maakohus Tallinna kohtumaja'. |
| limit | integer | |
| query | string | Free text (or "quoted phrase"); omit to browse by filters alone. |
| offset | integer | |
| date_to | string | YYYY-MM-DD upper bound (decision date). |
| category | string | Exact area of law, e.g. 'Võlaõigus'. |
| case_type | string |
Given a ruling id (from `search`), list the statute paragraphs it cites, with the lõiked named and each § resolved to its act. Use it to see the legal basis of a decision without reading the whole judgment, then `fetch` a `section:` id for the provision text.
| Argument | Type | Description |
|---|---|---|
| id* | string | Ruling id, e.g. 'ruling:1279503'. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Ruling id, e.g. 'ruling:1279503'."
}
},
"additionalProperties": false
}| date_from | string | YYYY-MM-DD lower bound (decision date). |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"court": {
"type": "string",
"description": "Exact court name, e.g. 'Harju Maakohus Tallinna kohtumaja'."
},
"limit": {
"type": "integer",
"maximum": 25,
"minimum": 1
},
"query": {
"type": "string",
"description": "Free text (or \"quoted phrase\"); omit to browse by filters alone."
},
"offset": {
"type": "integer",
"minimum": 0
},
"date_to": {
"type": "string",
"description": "YYYY-MM-DD upper bound (decision date)."
},
"category": {
"type": "string",
"description": "Exact area of law, e.g. 'Võlaõigus'."
},
"case_type": {
"enum": [
"civil",
"administrative",
"criminal"
],
"type": "string"
},
"date_from": {
"type": "string",
"description": "YYYY-MM-DD lower bound (decision date)."
}
},
"additionalProperties": false
}