Skip to main content
Glama
philrox

RIS MCP Server

by philrox
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Gemeinderecht durchsuchen

ris_gemeinden
Read-only

Search and retrieve Austrian municipal regulations and local ordinances by municipality, state, subject area, or keyword.

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
NameRequiredDescriptionDefault
indexNoSubject area index (Gr only) - VertretungskoerperUndAllgemeineVerwaltung, OeffentlicheOrdnungUndSicherheit, UnterrichtErziehungSportUndWissenschaft, KunstKulturUndKultus, SozialeWohlfahrtUndWohnbaufoerderung, Gesundheit, StraßenUndWasserbauVerkehr, Wirtschaftsfoerderung, Dienstleistungen, Finanzwirtschaft
limitNoResults per page: 10, 20, 50, or 100 (default: 20)
seiteNoPage number (default: 1)
titelNoSearch in titles
bezirkNoDistrict name (GrA only, e.g., "Bregenz")
gemeindeNoMunicipality name (e.g., "Graz")
suchworteNoFull-text search terms
bundeslandNoFilter by state - Burgenland, Kärnten, Niederösterreich, Oberösterreich, Salzburg, Steiermark, Tirol, Vorarlberg, Wien
applikationNo"Gr" (municipal law, default) or "GrA" (cross-border/Amtsblätter)Gr
fassung_vomNoHistorical version date (YYYY-MM-DD, Gr only)
im_ris_seitNoFilter by time in RIS - EinerWoche, ZweiWochen, EinemMonat, DreiMonaten, SechsMonaten, EinemJahr
geschaeftszahlNoFile number/Aktenzeichen (Gr only)
gemeindeverbandNoMunicipal association name (GrA only)
response_formatNo"markdown" (default) or "json"markdown
kundmachungsnummerNoAnnouncement number (GrA only)
sortierung_richtungNoSort direction
sortierung_spalte_grNoSort column (Gr only)
kundmachungsdatum_bisNoAnnouncement date to (YYYY-MM-DD, GrA only)
kundmachungsdatum_vonNoAnnouncement date from (YYYY-MM-DD, GrA only)

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Annotations include readOnlyHint=true and openWorldHint=true. Description adds search domain (municipal law), applications (Gr, GrA), and example queries. No contradiction; adds contextual behavior beyond annotations.

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?

Description is well-structured: purpose first, then usage, applications, and example queries. No fluff; every sentence adds value. Front-loaded with critical information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the description covers domain and examples, it lacks details on output structure or response content. No output schema, and description does not clarify what the returned data includes beyond mention of response_format parameter. For a complex tool with 19 parameters, this is a gap.

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% but description adds significant value: example queries showing parameter combinations (e.g., gemeinde+suchworte, bundesland+titel), explanation of applikation parameter options, and hints like 'Gr only' or 'GrA only' for some parameters.

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?

Description clearly states 'Search Austrian municipal law (Gemeinderecht)' and provides specific verb-resource pair. Distinguishes from sibling tools by domain (Gemeinderecht, Gr/GrA applications). Examples reinforce purpose.

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?

Clearly states 'Use this tool to find municipal regulations and local ordinances' and lists applications. However, no explicit when-not-to-use or guidance to alternatives, though sibling tools cover other legal domains.

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