Skip to main content
Glama
philrox

RIS MCP Server

by philrox
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Bundesrecht durchsuchen

ris_bundesrecht
Read-only

Search Austrian federal legislation by title, paragraph, or keywords. Retrieve consolidated versions as of a specific date, or access draft laws and English translations.

Instructions

Search Austrian federal laws (Bundesrecht).

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

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
NameRequiredDescriptionDefault
limitNoResults per page: 10, 20, 50, or 100 (default: 20)
seiteNoPage number (default: 1)
titelNoSearch in law titles (e.g., "ABGB", "Strafgesetzbuch")
paragraphNoSection number to search for (e.g., "1295" for §1295, "7" for Art 7)
suchworteNoFull-text search terms (e.g., "Mietrecht", "Schadenersatz")
applikationNoData source - "BrKons" (consolidated, default), "Begut" (drafts), "BgblAuth" (gazette), "Erv" (English translations)BrKons
fassung_vomNoConsolidated version as of this date (YYYY-MM-DD) — retrieves the law text as it stood on that day. Not supported for "Erv".
abschnitt_typNoType 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_formatNo"markdown" (default) or "json"markdown

Tool Definition Quality

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint; description adds behavioral details like consolidated versions and data sources. No contradictions.

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 description is well-structured with a clear initial purpose, followed by usage instructions and examples. It is concise but covers necessary details.

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?

Given the parameter count and schema coverage, the description provides sufficient context through examples for an agent to use the tool effectively, though output schema is absent.

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%, but the description adds value through example queries that show parameter interactions and semantics beyond the schema descriptions.

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?

The description clearly states it searches Austrian federal laws and provides examples, distinguishing it from sibling tools that search state laws or judiciary. However, it does not explicitly contrast with siblings.

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?

The description includes explicit usage instructions and example queries covering different parameter combinations, but does not mention when not to use it or alternatives among sibling tools.

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