Skip to main content
Glama
philrox

RIS MCP Server

by philrox

Judikatur durchsuchen

ris_judikatur
Read-only

Retrieve Austrian court decisions using filters like jurisdiction, court, legal norm, or keywords, with results as headnotes or full texts.

Instructions

Search Austrian court decisions (Judikatur).

Use this tool to find court decisions from Austrian courts. Choose the jurisdiction via "gerichtsbarkeit" (which court system to search).

RIS distinguishes two document kinds, controlled by "dokumenttyp":

  • Rechtssatz: abstract legal principle / headnote (Leitsatz) distilled from a decision

  • Entscheidungstext: the full decision text including reasoning (Begruendung) The default "beide" searches both for the most complete results.

Example queries:

  • gerichtsbarkeit="Vfgh", suchworte="Grundrecht" -> Constitutional Court decisions

  • suchworte="Schadenersatz", gericht="OGH" -> Only Supreme Court (OGH) decisions

  • norm="1295 ABGB" -> Which decisions cite §1295 ABGB?

  • gerichtsbarkeit="Justiz", fachgebiet="Arbeitsrecht", sortierung="datum_ab" -> Newest labor-law decisions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
normNoSearch by legal norm (e.g., "1319a ABGB")
limitNoResults per page: 10, 20, 50, or 100 (default: 20)
seiteNoPage number
gerichtNoFilter by the actual court within the jurisdiction (e.g., "OGH", "OLG Wien"). Applies to gerichtsbarkeit="Justiz".
suchworteNoFull-text search in decisions
fachgebietNoSubject area of OGH case law (e.g., "Arbeitsrecht", "Insolvenzrecht"). Applies to gerichtsbarkeit="Justiz" and only matches full decision texts (requires dokumenttyp "entscheidungstext" or "beide").
sortierungNoSort by decision date: "datum_auf" (oldest first) or "datum_ab" (newest first).
dokumenttypNoWhich document kind to search: "rechtssatz" (abstract headnotes only), "entscheidungstext" (full decision texts only), or "beide" (both, default). The RIS API otherwise searches only Rechtssätze.beide
rechtsgebietNoBroad legal area: "Zivilrecht" or "Strafrecht". Applies to gerichtsbarkeit="Justiz".
geschaeftszahlNoCase number (e.g., "5Ob234/20b")
gerichtsbarkeitNoCourt system / data collection to search (maps to the RIS "Applikation"): "Justiz" (OGH/OLG/LG/BG, default), "Vfgh" (Constitutional), "Vwgh" (Administrative), "Bvwg", "Lvwg", "Dsk" (Data Protection), "AsylGH", "Normenliste", "Pvak", "Gbk", "Dok", plus historical (dissolved 2014, stock still searchable): "Verg", "Uvs", "Ubas", "Umse", "Bks"Justiz
response_formatNo"markdown" or "json"markdown
sammlungsnummerNoCollection number: VfSlg (gerichtsbarkeit="Vfgh") or VwSlg (gerichtsbarkeit="Vwgh").
entscheidungsartNoType of decision. Allowed values differ by jurisdiction, e.g. Vfgh/Vwgh/Bvwg: "Beschluss", "Erkenntnis"; Lvwg also "Bescheid"; Justiz: "Verstärkter Senat", "Ordentliche Erledigung (Sachentscheidung)".
entscheidungsdatum_bisNoDecision date to (YYYY-MM-DD)
entscheidungsdatum_vonNoDecision date from (YYYY-MM-DD)
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. Description adds that it searches the RIS database, explains defaults (dokumenttyp=beide, gerichtsbarkeit=Justiz), and notes pagination (limit, seite). No contradictions. Adds moderate behavioral 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?

Well-structured with clear sections, examples, and bullet points. Slightly long but justified by complexity (16 parameters). Front-loaded with purpose and examples. Concise enough for its scope.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers main use cases with examples. No output schema, but mentions response_format parameter for markdown or JSON. Could briefly describe return fields (e.g., list of decisions with metadata). Slight gap but acceptable given parameter richness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant value: explains the relationship between fachgebiet and dokumenttyp, the meaning of gerichtsbarkeit and its values, and provides example queries that illustrate parameter combinations. Exceeds baseline.

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?

Description clearly states it searches Austrian court decisions (Judikatur) with specific verb 'search'. Distinguishes from sibling tools like ris_bundesrecht by focusing on case law. Provides examples for different courts and document types.

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?

Explicitly says when to use: to find court decisions. Offers examples for various jurisdictions and queries. Does not explicitly state when not to use, but the examples and sibling context imply differentiation. Strong guidance overall.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/philrox/ris-mcp-ts'

If you have feedback or need assistance with the MCP directory API, please join our Discord server