ris-mcp

Gemeinderecht durchsuchen

ris_gemeinden

Read-only

Search Austrian municipal law (Gemeinderecht). Filter results by municipality, state, and keywords to find local regulations.

Instructions

Search Austrian municipal law (Gemeinderecht).

Use this tool to find municipal regulations and local ordinances.

Applications:

Gr: Municipal law (Gemeinderecht) - default
GrA: Cross-border municipal law (Gemeinderecht Authentisch/Amtsblätter)

Example queries:

gemeinde="Graz", suchworte="Parkgebuehren"
bundesland="Tirol", titel="Gebuehrenordnung"
applikation="Gr", index="Baurecht"
applikation="GrA", bezirk="Bregenz"

Input Schema

TableJSON Schema

Name	Required	Description	Default
`index`	No	Subject area index (Gr only) - VertretungskoerperUndAllgemeineVerwaltung, OeffentlicheOrdnungUndSicherheit, UnterrichtErziehungSportUndWissenschaft, KunstKulturUndKultus, SozialeWohlfahrtUndWohnbaufoerderung, Gesundheit, StraßenUndWasserbauVerkehr, Wirtschaftsfoerderung, Dienstleistungen, Finanzwirtschaft
`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 titles
`bezirk`	No	District name (GrA only, e.g., "Bregenz")
`gemeinde`	No	Municipality name (e.g., "Graz")
`suchworte`	No	Full-text search terms
`bundesland`	No	Filter by state - Burgenland, Kärnten, Niederösterreich, Oberösterreich, Salzburg, Steiermark, Tirol, Vorarlberg, Wien
`applikation`	No	"Gr" (municipal law, default) or "GrA" (cross-border/Amtsblätter)	Gr
`fassung_vom`	No	Historical version date (YYYY-MM-DD, Gr only)
`im_ris_seit`	No	Filter by time in RIS - EinerWoche, ZweiWochen, EinemMonat, DreiMonaten, SechsMonaten, EinemJahr
`geschaeftszahl`	No	File number/Aktenzeichen (Gr only)
`gemeindeverband`	No	Municipal association name (GrA only)
`response_format`	No	"markdown" (default) or "json"	markdown
`kundmachungsnummer`	No	Announcement number (GrA only)
`sortierung_richtung`	No	Sort direction
`sortierung_spalte_gr`	No	Sort column (Gr only)
`kundmachungsdatum_bis`	No	Announcement date to (YYYY-MM-DD, GrA only)
`kundmachungsdatum_von`	No	Announcement date from (YYYY-MM-DD, GrA only)

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"
+}

Changed1 schema field changedv1.6.1Aug 4, 2026

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"
+}

Changed6 schema fields changedv1.2.4Jul 4, 2026

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"
```
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

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only safety profile is covered. The main description adds little beyond usage mechanics; the one genuinely behavioral disclosure (payload budget, page_size/notice behavior) lives in the limit parameter's schema description rather than the main text, so the description itself contributes marginal 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?

The purpose is front-loaded in the first sentence, followed by a compact Applications block and well-chosen example queries. No filler or repetition of schema content; the structure is efficient and scannable.

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?

For a complex 19-parameter tool with an output schema present, the description covers the usage patterns, application variants, and parameter scoping well. Example queries give agents a template for invocation. Minor gap: it does not advise on choosing between this and sibling legal-search tools, but within-tool completeness is strong.

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?

Schema coverage is 100%, so parameters are documented. The description adds value beyond the schema by mapping parameters to example values (gemeinde='Graz', suchworte='Parkgebuehren') and by clarifying which parameters apply to which applikation (Gr vs GrA), which the schema does not state. This meaningfully compensates for the large 19-parameter surface.

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

Purpose4/5

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

States a specific verb+resource: 'Search Austrian municipal law (Gemeinderecht)' and 'find municipal regulations and local ordinances.' The resource is clearly distinct from siblings like ris_landesrecht or ris_bundesrecht, though the description does not explicitly name any sibling for contrast.

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?

Provides explicit guidance through the Applications section (Gr default vs GrA for cross-border/Amtsblätter), concrete example queries pairing parameters with values, and inline scope notes marking which parameters are Gr-only (index, fassung_vom, geschaeftszahl, sortierung_spalte_gr) versus GrA-only (bezirk, gemeindeverband, kundmachungsnummer). It does not, however, state when to prefer sibling tools such as ris_landesrecht.

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

Deploy Server

Gemeinderecht durchsuchen

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools