Skip to main content
Glama

Landesrecht durchsuchen

ris_landesrecht
Read-only

Search Austrian provincial laws by title, section, or full-text keywords, filter by federal state, and retrieve consolidated versions as of a specific 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)
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
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
Behavior4/5

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

Annotations already indicate read-only and open-world behavior, but the description adds valuable behavioral details: suchworte results are ordered alphabetically not by relevance, and Austrian legal topics are often split across federal/state laws. These traits aren't obvious from annotations and help the agent anticipate search outcomes.

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 well-structured: it opens with a clear one-sentence purpose, then provides usage strategy, and ends with example queries. Every sentence carries useful information, and the length is appropriate for 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?

Given the tool has 11 parameters and an output schema, the description provides sufficient context for correct selection and invocation. It covers purpose, alternative tools, search strategies, and concrete examples, making it complete for real usage.

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 covers all parameters, but the description adds strategic meaning beyond the field descriptions. It explains how parameters like 'titel', 'paragraph', and 'suchworte' should be used together, provides example queries, and warns about the suchworte behavior (which is repeated in the schema but reinforced with examples).

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 clearly states the tool searches Austrian state/provincial laws (Landesrecht) and explicitly distinguishes it from ris_bundesrecht for federal laws. It uses a specific verb and resource, making the tool's purpose unambiguous and differentiated from siblings.

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?

The description provides explicit when-to-use guidance: it recommends using 'titel' and 'paragraph' for precise searches, warns against 'suchworte' due to alphabetical ordering, and directs users to ris_bundesrecht for federal law topics. This goes beyond general context and gives concrete decision rules.

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/Honeyfield-Org/ris-mcp-ts'

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