ris-mcp

Bundesrecht durchsuchen

ris_bundesrecht

Read-only

Search Austrian federal legislation by title, section, or keyword. Retrieve consolidated versions, draft bills, or official gazette text from the legal information system.

Instructions

Search Austrian federal laws (Bundesrecht).

Use this tool to find Austrian federal legislation like ABGB, StGB, UGB, etc.

Search strategy: "titel" and "paragraph" are the precise entry points — prefer them whenever the law or the section is known ("paragraph" is ignored for applikation="Erv", the English translations). "suchworte" runs a broad full-text search and the RIS API returns those hits ordered alphabetically by law title, not by relevance, so a common term buries the relevant law under thousands of results. Austrian law often splits one topic across several statutes, so look for a companion law: warranty, for example, is covered both by the VGG (consumer sales, B2C, in force since 2022) and by §§ 922 ff ABGB (general warranty law, including B2B).

Example queries:

suchworte="Mietrecht" -> Find laws mentioning rent law
titel="ABGB", paragraph="1295" -> Find specific ABGB section
titel="B-VG", paragraph="7", abschnitt_typ="Artikel" -> Article-based laws
titel="ABGB", fassung_vom="2015-01-01" -> Consolidated version as of a date
applikation="Begut" -> Search draft legislation

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Results per page: 10, 20, 50 or 100 (default: 20). Every hit costs about 1k characters of structured payload, so prefer 20 for browsing and 50 for a broad survey; a page that would exceed the payload budget is delivered at the next smaller page size and says so (page_size, query.limit and notice).
`seite`	No	Page number (default: 1)
`titel`	No	Search in law titles (e.g., "ABGB", "Strafgesetzbuch")
`paragraph`	No	Section number to search for (e.g., "1295" for §1295, "7" for Art 7)
`suchworte`	No	Broad full-text search terms (e.g., "Mietrecht", "Schadenersatz"). Hits come back ordered alphabetically by law title, not by relevance — prefer "titel" and/or "paragraph" whenever the law or the section is known.
`applikation`	No	Data source - "BrKons" (consolidated, default), "Begut" (drafts), "BgblAuth" (gazette), "Erv" (English translations)	BrKons
`fassung_vom`	No	Consolidated version as of this date (YYYY-MM-DD) — retrieves the law text as it stood on that day. Not supported for "Erv".
`abschnitt_typ`	No	Type of section that "paragraph" refers to: "Paragraph" (default), "Artikel" (article-based laws like B-VG), or "Anlage" (annex). "Art 7 B-VG" requires "Artikel".	Paragraph
`response_format`	No	"markdown" (default) or "json"	markdown

Output Schema

TableJSON Schema

Name	Required	Description
`page`	Yes	Page number of this result set (1-based)
`query`	No	Echo of the validated search parameters alongside the tool name — re-issue the call with an incremented "seite" for the next page
`notice`	No	Present when the page was delivered at a smaller size than requested to fit the payload budget — page, page_size and query already describe the delivered page; page with query.limit
`has_more`	Yes	Whether further result pages are available
`documents`	Yes	The documents on this page
`page_size`	Yes	Number of documents per page
`total_hits`	Yes	Total number of documents in RIS matching the search

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.8.2Sep 9, 2026

changedInput schema / properties / limit / description

Previous value: -"Results per page: 10, 20, 50 or 100 (default: 20). Every hit costs about 1-2k characters of structured payload, so prefer 20 for browsing and 50 for a broad survey; a page that would exceed the payload budget is delivered at the next smaller page size and says so (page_size, query.limit and notice)."New value: +"Results per page: 10, 20, 50 or 100 (default: 20). Every hit costs about 1k characters of structured payload, so prefer 20 for browsing and 50 for a broad survey; a page that would exceed the payload budget is delivered at the next smaller page size and says so (page_size, query.limit and notice)."

Changed6 schema fields changedv1.8.0Sep 8, 2026

changedInput schema / properties / limit / description

Previous value: -"Results per page: 10, 20, 50, or 100 (default: 20)"New value: +"Results per page: 10, 20, 50 or 100 (default: 20). Every hit costs about 1-2k characters of structured payload, so prefer 20 for browsing and 50 for a broad survey; a page that would exceed the payload budget is delivered at the next smaller page size and says so (page_size, query.limit and notice)."

removedOutput schema / properties / documents / items / properties / citation / properties / kurztitel

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

removedOutput schema / properties / documents / items / properties / content_urls / properties / rtf

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

removedOutput schema / properties / documents / items / properties / content_urls / properties / xml

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

removedOutput schema / properties / documents / items / properties / kurztitel

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

addedOutput schema / properties / notice

Added value: +{
+  "description": "Present when the page was delivered at a smaller size than requested to fit the payload budget — page, page_size and query already describe the delivered page; page with query.limit",
+  "type": "string"
+}

Changed2 schema fields changedv1.6.1Aug 4, 2026

changedInput schema / properties / suchworte / description

Previous value: -"Full-text search terms (e.g., \"Mietrecht\", \"Schadenersatz\")"New value: +"Broad full-text search terms (e.g., \"Mietrecht\", \"Schadenersatz\"). Hits come back ordered alphabetically by law title, not by relevance — prefer \"titel\" and/or \"paragraph\" whenever the law or the section is known."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "documents": {
+      "description": "The documents on this page",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "applikation": {
+            "type": "string"
+          },
+          "citation": {
+            "additionalProperties": false,
+            "properties": {
+              "ausserkrafttreten": {
+                "anyOf": [
+                  {
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "eli": {
+                "anyOf": [
+                  {
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "inkrafttreten": {
+                "anyOf": [
+                  {
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "kundmachungsorgan": {
+                "anyOf": [
+                  {
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "kurztitel": {
+                "anyOf": [
+                  {
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "langtitel": {
+                "anyOf": [
+                  {
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "paragraph": {
+                "anyOf": [
+                  {
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "citation_display": {
+            "description": "Preformatted citation line as shown in the text output",
+            "type": "string"
+          },
+          "content_urls": {
+            "additionalProperties": false,
+            "properties": {
+              "html": {
+                "anyOf": [
+                  {
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "pdf": {
+                "anyOf": [
+                  {
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "rtf": {
+                "anyOf": [
+                  {
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "xml": {
+                "anyOf": [
+                  {
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "dokument_url": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "dokumentnummer": {
+            "type": "string"
+          },
+          "entscheidungsdatum": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Decision date as YYYY-MM-DD (Judikatur documents only)"
+          },
+          "gericht": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Deciding court or authority (Judikatur documents only)"
+          },
+          "gesamte_rechtsvorschrift_url": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "geschaeftszahl": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Case number(s), semicolon-separated when several (Judikatur documents only)"
+          },
+          "kurztitel": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "rechtssatznummer": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Rechtssatz number, e.g. \"RS0018547\" (Judikatur Rechtssatz documents only)"
+          },
+          "titel": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "dokumentnummer",
+          "applikation",
+          "titel",
+          "citation",
+          "citation_display",
+          "content_urls"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "has_more": {
+      "description": "Whether further result pages are available",
+      "type": "boolean"
+    },
+    "page": {
+      "description": "Page number of this result set (1-based)",
+      "type": "number"
+    },
+    "page_size": {
+      "description": "Number of documents per page",
+      "type": "number"
+    },
+    "query": {
+      "additionalProperties": {},
+      "description": "Echo of the validated search parameters alongside the tool name — re-issue the call with an incremented \"seite\" for the next page",
+      "properties": {
+        "tool": {
+          "description": "Name of the tool that produced this result — call it again to paginate",
+          "type": "string"
+        }
+      },
+      "required": [
+        "tool"
+      ],
+      "type": "object"
+    },
+    "total_hits": {
+      "description": "Total number of documents in RIS matching the search",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total_hits",
+    "page",
+    "page_size",
+    "has_more",
+    "documents"
+  ],
+  "type": "object"
+}

Changed10 schema fields changedv1.2.4Jul 4, 2026

addedInput schema / properties / abschnitt_typ

Added value: +{
+  "default": "Paragraph",
+  "description": "Type of section that \"paragraph\" refers to: \"Paragraph\" (default), \"Artikel\" (article-based laws like B-VG), or \"Anlage\" (annex). \"Art 7 B-VG\" requires \"Artikel\".",
+  "enum": [
+    "Paragraph",
+    "Artikel",
+    "Anlage"
+  ],
+  "type": "string"
+}

changedInput schema / properties / applikation / description

Previous value: -"Data source - \"BrKons\" (consolidated, default), \"Begut\" (drafts), \"BgblAuth\" (gazette), \"Erv\" (English)"New value: +"Data source - \"BrKons\" (consolidated, default), \"Begut\" (drafts), \"BgblAuth\" (gazette), \"Erv\" (English translations)"

changedInput schema / properties / fassung_vom / description

Previous value: -"Date for historical version (YYYY-MM-DD)"New value: +"Consolidated version as of this date (YYYY-MM-DD) — retrieves the law text as it stood on that day. Not supported for \"Erv\"."

addedInput schema / properties / limit / anyOf

Added value: +[
+  {
+    "const": 10,
+    "type": "number"
+  },
+  {
+    "const": 20,
+    "type": "number"
+  },
+  {
+    "const": 50,
+    "type": "number"
+  },
+  {
+    "const": 100,
+    "type": "number"
+  }
+]

changedInput schema / properties / limit / description

Previous value: -"Results per page 10/20/50/100 (default: 20)"New value: +"Results per page: 10, 20, 50, or 100 (default: 20)"

removedInput schema / properties / limit / type
```
Removed value: -"number"
```

changedInput schema / properties / paragraph / description

Previous value: -"Paragraph number to search for (e.g., \"1295\" for §1295)"New value: +"Section number to search for (e.g., \"1295\" for §1295, \"7\" for Art 7)"

addedInput schema / properties / seite / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / seite / minimum
```
Added value: +1
```

changedInput schema / properties / seite / type

Previous value: -"number"New value: +"integer"

First observedv1.1.3Mar 20, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations (readOnlyHint, openWorldHint, destructiveHint) cover safety, but the description adds rich behavioral context: suchworte ordering, payload budget per hit, page-size reduction with notice, and exceptions for 'Erv' (paragraph ignored, fassung_vom unsupported). These details go well beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured and front-loaded: purpose, search strategy, then example queries. Every section earns its place; the example queries are compact and illustrative without redundancy. Length is justified by the tool's complexity.

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?

Complete for a 9-parameter search tool with an output schema. It covers search strategy, edge cases (Erv, article-based laws), pagination behavior, and companion-law hints. No critical information an agent needs to call it correctly is missing.

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%, so baseline is 3, but the description adds substantial meaning: explains how 'paragraph' interacts with 'abschnitt_typ', gives example queries mapping parameters to real use cases, and notes specific constraints like paragraph being ignored for 'Erv'. This materially aids correct invocation.

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?

Clearly states the tool searches Austrian federal laws (Bundesrecht), with a specific verb and resource. It names example laws (ABGB, StGB, UGB) and the federal scope distinguishes it from sibling tools like ris_landesrecht. The purpose is immediately understandable and differentiated.

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

Usage Guidelines5/5

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

Provides an explicit search strategy: prefer 'titel' and 'paragraph' for precise lookups, warns that 'suchworte' returns alphabetical rather than relevance-ordered results, and even advises looking for companion laws (e.g., VGG vs ABGB). This is clear when-to-use and when-not-to-use guidance with alternatives.

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

Deploy Server

Bundesrecht durchsuchen

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools