Skip to main content
Glama

ris_verordnungen

Search Austrian state ordinance gazettes to find official provincial regulations. Currently provides access to Tirol data from 2022 onward, with options for full-text, title, date range, and publication number searches.

Instructions

Search Austrian state ordinance gazettes (Verordnungsblaetter der Laender).

Use this tool to find official publications of state/provincial ordinances. NOTE: Currently only Tirol data is available (since January 1, 2022). Other federal states have not yet published their ordinance gazettes in RIS.

Example queries:

  • suchworte="Wolf" -> Full-text search

  • titel="Verordnung" -> Search in title

  • bundesland="Tirol" -> Filter by state (currently only Tirol has data)

  • kundmachungsnummer="25" -> Search by publication number

  • kundmachungsdatum_von="2024-01-01", kundmachungsdatum_bis="2024-12-31" -> Date range

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
suchworteNoFull-text search terms
titelNoSearch in title
bundeslandNoFilter by state (currently only Tirol has data)
kundmachungsnummerNoPublication number
kundmachungsdatum_vonNoPublication date from (YYYY-MM-DD)
kundmachungsdatum_bisNoPublication date to (YYYY-MM-DD)
seiteNoPage number (default: 1)
limitNoResults per page 10/20/50/100 (default: 20)
response_formatNo"markdown" (default) or "json"markdown

Implementation Reference

  • Handler logic for the ris_verordnungen tool which prepares search parameters and calls executeSearchTool.
      async (args) => {
        const {
          suchworte,
          titel,
          bundesland,
          kundmachungsnummer,
          kundmachungsdatum_von,
          kundmachungsdatum_bis,
          seite,
          limit,
          response_format,
        } = args;
    
        if (
          !hasAnyParam(args, [
            'suchworte',
            'titel',
            'bundesland',
            'kundmachungsnummer',
            'kundmachungsdatum_von',
          ])
        ) {
          return createValidationErrorResponse([
            'suchworte` fuer Volltextsuche',
            'titel` fuer Titelsuche',
            'bundesland` fuer Bundesland-Filter',
            'kundmachungsnummer` fuer Verordnungsnummer',
            'kundmachungsdatum_von` fuer Datum ab',
          ]);
        }
    
        // Uses Landesrecht endpoint with Applikation="Vbl"
        // Note: Vbl uses direct Bundesland values, NOT the SucheIn format used by Lgbl
        const params = buildBaseParams('Vbl', limit, seite);
        addOptionalParams(params, [
          [suchworte, 'Suchworte'],
          [titel, 'Titel'],
          [bundesland, 'Bundesland'],
          [kundmachungsnummer, 'Kundmachungsnummer'],
          [kundmachungsdatum_von, 'Kundmachungsdatum.Von'],
          [kundmachungsdatum_bis, 'Kundmachungsdatum.Bis'],
        ]);
    
        return executeSearchTool(searchLandesrecht, params, response_format);
      },
    );
  • Zod schema definition for the ris_verordnungen tool arguments.
    {
      suchworte: z.string().max(1000).optional().describe('Full-text search terms'),
      titel: z.string().max(500).optional().describe('Search in title'),
      bundesland: z
        .enum(VALID_VBL_BUNDESLAENDER)
        .optional()
        .describe('Filter by state (currently only Tirol has data)'),
      kundmachungsnummer: z.string().max(100).optional().describe('Publication number'),
      kundmachungsdatum_von: DateSchema.optional().describe('Publication date from (YYYY-MM-DD)'),
      kundmachungsdatum_bis: DateSchema.optional().describe('Publication date to (YYYY-MM-DD)'),
      seite: z.number().default(1).describe('Page number (default: 1)'),
      limit: z.number().default(20).describe('Results per page 10/20/50/100 (default: 20)'),
      response_format: z
        .enum(['markdown', 'json'])
        .default('markdown')
        .describe('"markdown" (default) or "json"'),
    },
  • Tool registration function for ris_verordnungen.
    export function registerVerordnungenTool(server: McpServer): void {
      server.tool(
        'ris_verordnungen',
        `Search Austrian state ordinance gazettes (Verordnungsblaetter der Laender).
    
    Use this tool to find official publications of state/provincial ordinances.
    NOTE: Currently only Tirol data is available (since January 1, 2022).
    Other federal states have not yet published their ordinance gazettes in RIS.
    
    Example queries:
      - suchworte="Wolf" -> Full-text search
      - titel="Verordnung" -> Search in title
      - bundesland="Tirol" -> Filter by state (currently only Tirol has data)
      - kundmachungsnummer="25" -> Search by publication number
      - kundmachungsdatum_von="2024-01-01", kundmachungsdatum_bis="2024-12-31" -> Date range`,
        {
          suchworte: z.string().max(1000).optional().describe('Full-text search terms'),
          titel: z.string().max(500).optional().describe('Search in title'),
          bundesland: z
            .enum(VALID_VBL_BUNDESLAENDER)
            .optional()
            .describe('Filter by state (currently only Tirol has data)'),
          kundmachungsnummer: z.string().max(100).optional().describe('Publication number'),
          kundmachungsdatum_von: DateSchema.optional().describe('Publication date from (YYYY-MM-DD)'),
          kundmachungsdatum_bis: DateSchema.optional().describe('Publication date to (YYYY-MM-DD)'),
          seite: z.number().default(1).describe('Page number (default: 1)'),
          limit: z.number().default(20).describe('Results per page 10/20/50/100 (default: 20)'),
          response_format: z
            .enum(['markdown', 'json'])
            .default('markdown')
            .describe('"markdown" (default) or "json"'),
        },
        async (args) => {
          const {
            suchworte,
            titel,
            bundesland,
            kundmachungsnummer,
            kundmachungsdatum_von,
            kundmachungsdatum_bis,
            seite,
            limit,
            response_format,
          } = args;
    
          if (
            !hasAnyParam(args, [
              'suchworte',
              'titel',
              'bundesland',
              'kundmachungsnummer',
              'kundmachungsdatum_von',
            ])
          ) {
            return createValidationErrorResponse([
              'suchworte` fuer Volltextsuche',
              'titel` fuer Titelsuche',
              'bundesland` fuer Bundesland-Filter',
              'kundmachungsnummer` fuer Verordnungsnummer',
              'kundmachungsdatum_von` fuer Datum ab',
            ]);
          }
    
          // Uses Landesrecht endpoint with Applikation="Vbl"
          // Note: Vbl uses direct Bundesland values, NOT the SucheIn format used by Lgbl
          const params = buildBaseParams('Vbl', limit, seite);
          addOptionalParams(params, [
            [suchworte, 'Suchworte'],
            [titel, 'Titel'],
            [bundesland, 'Bundesland'],
            [kundmachungsnummer, 'Kundmachungsnummer'],
            [kundmachungsdatum_von, 'Kundmachungsdatum.Von'],
            [kundmachungsdatum_bis, 'Kundmachungsdatum.Bis'],
          ]);
    
          return executeSearchTool(searchLandesrecht, params, response_format);
        },
      );
    }
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively communicates that this is a search/read-only operation (implied by 'search' and 'find'), discloses the data availability limitation (only Tirol since 2022), and provides example queries that help understand how the tool behaves. However, it doesn't mention pagination behavior (implied by page/limit parameters) or rate limits.

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 perfectly structured: purpose statement first, usage guidance second, important limitation third, and practical examples last. Every sentence earns its place, with no wasted words. The bullet-point examples are particularly efficient for conveying parameter usage patterns.

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?

For a search tool with 9 parameters, 100% schema coverage, and no output schema, the description provides excellent context about the tool's purpose, limitations, and usage patterns. The only minor gap is the lack of information about output format or result structure, but given the schema's completeness and the tool's search nature, this is acceptable.

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 description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds value through example queries that show practical usage patterns (e.g., 'suchworte="Wolf" -> Full-text search'), but doesn't provide additional semantic context beyond what's in the parameter descriptions. This meets the baseline expectation when schema coverage is complete.

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's purpose: 'Search Austrian state ordinance gazettes (Verordnungsblaetter der Laender).' It specifies both the verb ('search') and resource ('Austrian state ordinance gazettes'), distinguishing it from sibling tools like ris_bundesrecht (federal law) or ris_landesrecht (state law) by focusing specifically on ordinance publications rather than laws.

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 guidance on when to use this tool: 'Use this tool to find official publications of state/provincial ordinances.' It also includes important exclusion criteria: 'NOTE: Currently only Tirol data is available (since January 1, 2022). Other federal states have not yet published their ordinance gazettes in RIS.' This tells the agent exactly when this tool is applicable and when it's not.

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