Skip to main content
Glama
philrox

RIS MCP Server

by philrox

ris_sonstige

Retrieve legal documents from Austrian miscellaneous collections including trade exams, social insurance, health plans, and ministerial decrees. Search historical materials from court announcements and cabinet protocols.

Instructions

Search miscellaneous Austrian legal collections (Sonstige).

Use this tool for specialized legal documents and historical materials.

Available applications:

  • PruefGewO: Trade licensing examinations (Gewerbeordnung)

  • Avsv: Social insurance announcements (Sozialversicherung)

  • Spg: Health structure plans (Strukturpläne Gesundheit)

  • Avn: Official veterinary notices (Amtliche Veterinärnachrichten)

  • KmGer: Court announcements (Kundmachungen der Gerichte)

  • Upts: Party transparency decisions (Parteien-Transparenz-Senat)

  • Mrp: Council of Ministers protocols (Ministerratsprotokolle)

  • Erlaesse: Ministerial decrees (Erlässe der Bundesministerien)

Example queries:

  • applikation="Mrp", suchworte="Budget", einbringer="BMF..."

  • applikation="Erlaesse", bundesministerium="Bundesministerium für Finanzen"

  • applikation="Upts", partei="SPÖ - Sozialdemokratische Partei Österreichs"

  • applikation="KmGer", kmger_typ="Geschaeftsordnung"

  • applikation="Avsv", dokumentart="Richtlinie"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applikationYesCollection to search - "PruefGewO" (trade exams), "Avsv" (social insurance), "Spg" (health plans), "Avn" (veterinary notices), "KmGer" (court announcements), "Upts" (party transparency), "Mrp" (cabinet protocols), "Erlaesse" (decrees)
suchworteNoFull-text search terms
titelNoSearch in titles
datum_vonNoDate from (YYYY-MM-DD)
datum_bisNoDate to (YYYY-MM-DD)
im_ris_seitNoFilter by time in RIS - EinerWoche, ZweiWochen, EinemMonat, DreiMonaten, SechsMonaten, EinemJahr
sortierung_richtungNoSort direction
geschaeftszahlNoFile number/Aktenzeichen (for Mrp, Upts, KmGer)
normNoLegal norm reference (for Erlaesse, Upts)
fassung_vomNoHistorical version date (YYYY-MM-DD, for Erlaesse)
einbringerNoSubmitter (Mrp only, e.g., ministry abbreviation)
sitzungsnummerNoSession number (Mrp only)
gesetzgebungsperiodeNoLegislative period (Mrp only, e.g., '27')
bundesministeriumNoFederal ministry (Erlaesse only)
abteilungNoDepartment/division (Erlaesse only)
fundstelleNoSource reference (Erlaesse only)
parteiNoPolitical party (Upts only)
kmger_typNoAnnouncement type (KmGer only) - Geschaeftsordnung, Geschaeftsverteilung
gerichtNoCourt name (KmGer only)
dokumentartNoDocument type search (Avsv only) - free text search expression
urheberNoAuthor/institution (Avsv only)
avsvnummerNoAVSV number (Avsv only)
avnnummerNoAVN number (Avn only)
avn_typNoNotice type (Avn only) - Kundmachung, Verordnung, Erlass
spgnummerNoSPG number (Spg only)
osg_typNoAustrian health structure plan type (Spg only) - ÖSG, ÖSG - Großgeräteplan
rsg_typNoRegional health structure plan type (Spg only) - RSG, RSG - Großgeräteplan
rsg_landNoFederal state for RSG (Spg only)
pruefgewo_typNoExamination type (PruefGewO only) - Befähigungsprüfung, Eignungsprüfung, Meisterprüfung
seiteNoPage number (default: 1)
limitNoResults per page 10/20/50/100 (default: 20)
response_formatNo"markdown" (default) or "json"markdown
Behavior3/5

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

No annotations are provided, so the description must cover behavioral aspects. It describes the search behavior and parameter combinations but omits details on return format, pagination behavior, or authentication requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy due to listing all applications and examples. While thorough, it could be more concise without losing essential guidance.

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 high parameter count (32) and no output schema, the description provides comprehensive per-application parameter guidance. It lacks information on error handling, response structure, or performance considerations.

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 baseline is 3. The description adds examples and application-specific context but does not significantly enhance understanding beyond the schema's parameter descriptions.

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 miscellaneous Austrian legal collections (Sonstige) and lists specific application types, distinguishing it from siblings like ris_bundesrecht and ris_judikatur.

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 provides example queries and application-specific fields, giving clear usage context. However, it does not explicitly state when to use this tool over siblings or when to avoid it.

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