Skip to main content
Glama
philrox

RIS MCP Server

by philrox

ris_gemeinden

Search Austrian municipal law and local ordinances by municipality, state, subject area, or date.

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

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

No annotations are provided, so the description must disclose behavioral traits. It only states the tool performs searches, omitting details on authentication, rate limits, errors, or default behavior. The description adds little beyond the stated purpose.

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 efficiently structured with applications and examples, front-loading the purpose. It avoids unnecessary details, though a brief section on usage notes could improve clarity without much length.

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

Completeness2/5

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

Given 19 parameters and no output schema, the description lacks important context such as pagination details, result field descriptions, and search behavior (e.g., boolean operators). Examples help but are insufficient for full completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the description's examples provide modest additional context (e.g., showing parameter combinations). However, the description does not clarify parameter interactions or constraints beyond the schema, keeping it at baseline.

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 the tool searches Austrian municipal law (Gemeinderecht) and distinguishes two applications (Gr and GrA). It includes example queries that reinforce the purpose, but does not explicitly differentiate from sibling tools like ris_landesrecht or ris_bundesrecht, leaving some ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides core usage instructions and examples, but lacks explicit guidance on when not to use this tool or when to prefer siblings. Without exclusions or alternatives, the agent may struggle to decide between this and related RIS 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