Skip to main content
Glama
Honeyfield-Org

ris-mcp

by Honeyfield-Org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Landesrecht durchsuchen

ris_landesrecht
Read-only

Search Austrian state laws (Landesrecht) by title, paragraph, keyword, or federal state. Retrieve specific sections or historical versions as of a given date.

Instructions

Search Austrian state/provincial laws (Landesrecht).

Use this tool to find laws enacted by Austrian federal states (Bundeslaender).

Search strategy: "titel" and "paragraph" (together with "bundesland") are the precise entry points — prefer them whenever the law or the section is known. "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 and across the federal/state divide — when the topic turns out to be federal rather than state law (warranty, for example, sits in the VGG and in §§ 922 ff ABGB), search it with ris_bundesrecht instead.

Example queries:

  • suchworte="Bauordnung", bundesland="Salzburg" -> Find state building law

  • titel="Bauordnung", bundesland="Wien", paragraph="1" -> Specific section

  • suchworte="Naturschutz", bundesland="Tirol", fassung_vom="2020-01-01" -> Version as of a date

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoResults 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).
seiteNoPage number
titelNoSearch in law titles
paragraphNoSection number to search for (e.g., "1" for §1, "7" for Art 7)
suchworteNoBroad full-text search terms. Hits come back ordered alphabetically by law title, not by relevance — prefer "titel" and/or "paragraph" whenever the law or the section is known.
bundeslandNoFilter by state - Wien, Niederoesterreich, Oberoesterreich, Salzburg, Tirol, Vorarlberg, Kaernten, Steiermark, Burgenland
applikationNo"LrKons" (consolidated, default)LrKons
fassung_vomNoConsolidated version as of this date (YYYY-MM-DD) — retrieves the law text as it stood on that day.
abschnitt_typNoType of section that "paragraph" refers to: "Paragraph" (default), "Artikel", or "Anlage" (annex).Paragraph
gesetzesnummerNoExact law number (Gesetzesnummer) for a specific state law
response_formatNo"markdown" or "json"markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesPage number of this result set (1-based)
queryNoEcho of the validated search parameters alongside the tool name — re-issue the call with an incremented "seite" for the next page
noticeNoPresent 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_moreYesWhether further result pages are available
documentsYesThe documents on this page
page_sizeYesNumber of documents per page
total_hitsYesTotal number of documents in RIS matching the search

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.8.2
    • 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)."
  2. Changed6 schema fields changedv1.8.0
    • 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"
+}
  3. Changed2 schema fields changedv1.6.1
    • changedInput schema / properties / suchworte / description
      Previous value: -"Full-text search terms"New value: +"Broad full-text search terms. 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"
+}
  4. Changed10 schema fields changedv1.2.4
    • addedInput schema / properties / abschnitt_typ
      Added value: +{
+  "default": "Paragraph",
+  "description": "Type of section that \"paragraph\" refers to: \"Paragraph\" (default), \"Artikel\", or \"Anlage\" (annex).",
+  "enum": [
+    "Paragraph",
+    "Artikel",
+    "Anlage"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / fassung_vom
      Added value: +{
+  "description": "Consolidated version as of this date (YYYY-MM-DD) — retrieves the law text as it stood on that day.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • addedInput schema / properties / gesetzesnummer
      Added value: +{
+  "description": "Exact law number (Gesetzesnummer) for a specific state law",
+  "maxLength": 100,
+  "type": "string"
+}
    • 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"New value: +"Results per page: 10, 20, 50, or 100 (default: 20)"
    • removedInput schema / properties / limit / type
      Removed value: -"number"
    • addedInput schema / properties / paragraph
      Added value: +{
+  "description": "Section number to search for (e.g., \"1\" for §1, \"7\" for Art 7)",
+  "maxLength": 100,
+  "type": "string"
+}
    • 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"
  5. First observedv1.1.3

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses critical behavioral quirks: suchworte results are alphabetically ordered by law title (not relevance) and can bury relevant hits, and the limit parameter self-adjusts to a smaller page size when the payload budget is exceeded, with a notice. These are non-obvious behaviors that materially affect how the agent interprets results.

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?

The description is efficiently structured: purpose first, then search strategy, then examples. Every sentence earns its place, and the critical alternative-routing and ordering caveat are front-loaded before the examples. No redundancy or filler.

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?

For an 11-parameter tool with an output schema, the description covers all necessary decision points: when to use it, how to craft precise queries, which alternatives exist, and subtle behaviors like ordering and pagination fallback. The presence of an output schema means return format is already handled, so nothing essential is missing.

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?

The schema already documents all 11 parameters with 100% coverage, so the baseline is 3. The description adds value by explaining the relative precision of titel/paragraph vs suchworte, giving example query combinations (including fassung_vom), and clarifying the limit behavior. However, it does not systematically walk through each parameter, relying on the schema for full semantics.

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?

The description opens with a precise verb–resource pair ('Search Austrian state/provincial laws (Landesrecht)') and immediately differentiates from the sibling ris_bundesrecht by stating that federal law should go there. The examples further reinforce the scope, so an agent can instantly identify what this tool does and how it differs from nearby tools.

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?

It gives explicit when-to-use guidance: prefer 'titel' and 'paragraph' over 'suchworte' for precision, and explicitly routes federal topics (e.g., warranty in VGG/ABGB) to ris_bundesrecht. This is a clear, actionable routing rule with a concrete example, leaving no ambiguity about alternative selection.

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