Skip to main content
Glama

ris_bezirke

Search Austrian district authority announcements and ordinances from states like Niederösterreich, Tirol, and Vorarlberg to find official legal information and public notices.

Instructions

Search Austrian district administrative authority announcements (Kundmachungen der Bezirksverwaltungsbehörden).

Use this tool to find announcements and ordinances from district administrative authorities.

Note: Only certain states publish here: Niederösterreich, Oberösterreich, Tirol, Vorarlberg, Burgenland, Steiermark.

Example queries:

  • bundesland="Niederösterreich", suchworte="Bauordnung"

  • bezirksverwaltungsbehoerde="Bezirkshauptmannschaft Innsbruck"

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
bezirksverwaltungsbehoerdeNoDistrict authority name (e.g., "Bezirkshauptmannschaft Innsbruck", "Bezirkshauptmannschaft Amstetten")
kundmachungsnummerNoAnnouncement number
kundmachungsdatum_vonNoAnnouncement date from (YYYY-MM-DD)
kundmachungsdatum_bisNoAnnouncement date to (YYYY-MM-DD)
im_ris_seitNoFilter by time in RIS
seiteNoPage number (default: 1)
limitNoResults per page 10/20/50/100 (default: 20)
response_formatNo"markdown" (default) or "json"markdown

Implementation Reference

  • Tool registration for 'ris_bezirke' within registerBezirkeTool.
    export function registerBezirkeTool(server: McpServer): void {
      server.tool(
        'ris_bezirke',
        `Search Austrian district administrative authority announcements (Kundmachungen der Bezirksverwaltungsbehörden).
    
    Use this tool to find announcements and ordinances from district administrative authorities.
    
    Note: Only certain states publish here: Niederösterreich, Oberösterreich, Tirol, Vorarlberg, Burgenland, Steiermark.
    
    Example queries:
      - bundesland="Niederösterreich", suchworte="Bauordnung"
      - bezirksverwaltungsbehoerde="Bezirkshauptmannschaft Innsbruck"`,
        {
          suchworte: z.string().max(1000).optional().describe('Full-text search terms'),
          titel: z.string().max(500).optional().describe('Search in titles'),
          bundesland: BundeslandSchema.optional().describe(
            'Filter by state - Burgenland, Kärnten, Niederösterreich, Oberösterreich, Salzburg, Steiermark, Tirol, Vorarlberg, Wien',
          ),
          bezirksverwaltungsbehoerde: z
            .string()
            .max(200)
            .optional()
            .describe(
              'District authority name (e.g., "Bezirkshauptmannschaft Innsbruck", "Bezirkshauptmannschaft Amstetten")',
            ),
          kundmachungsnummer: z.string().max(100).optional().describe('Announcement number'),
          kundmachungsdatum_von: DateSchema.optional().describe('Announcement date from (YYYY-MM-DD)'),
          kundmachungsdatum_bis: DateSchema.optional().describe('Announcement date to (YYYY-MM-DD)'),
          im_ris_seit: z.enum(IM_RIS_SEIT_VALUES).optional().describe('Filter by time in RIS'),
          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,
            bezirksverwaltungsbehoerde,
            kundmachungsnummer,
            kundmachungsdatum_von,
            kundmachungsdatum_bis,
            im_ris_seit,
            seite,
            limit,
            response_format,
          } = args;
    
          if (
            !hasAnyParam(args, [
              'suchworte',
              'titel',
              'bundesland',
              'bezirksverwaltungsbehoerde',
              'kundmachungsnummer',
            ])
          ) {
            return createValidationErrorResponse([
              'suchworte` für Volltextsuche',
              'titel` für Titelsuche',
              'bundesland` für Bundesland',
              'bezirksverwaltungsbehoerde` für Bezirksverwaltungsbehörde',
              'kundmachungsnummer` für Kundmachungsnummer',
            ]);
          }
    
          const params = buildBaseParams('Bvb', limit, seite);
          addOptionalParams(params, [
            [suchworte, 'Suchworte'],
            [titel, 'Titel'],
            [bundesland, 'Bundesland'],
            [bezirksverwaltungsbehoerde, 'Bezirksverwaltungsbehoerde'],
            [kundmachungsnummer, 'Kundmachungsnummer'],
            [kundmachungsdatum_von, 'Kundmachungsdatum.Von'],
            [kundmachungsdatum_bis, 'Kundmachungsdatum.Bis'],
            [im_ris_seit, 'ImRisSeit'],
          ]);
    
          return executeSearchTool(searchBezirke, params, response_format);
        },
      );
    }
  • Handler function for 'ris_bezirke' which processes arguments, performs validation, and executes the search.
    async (args) => {
      const {
        suchworte,
        titel,
        bundesland,
        bezirksverwaltungsbehoerde,
        kundmachungsnummer,
        kundmachungsdatum_von,
        kundmachungsdatum_bis,
        im_ris_seit,
        seite,
        limit,
        response_format,
      } = args;
    
      if (
        !hasAnyParam(args, [
          'suchworte',
          'titel',
          'bundesland',
          'bezirksverwaltungsbehoerde',
          'kundmachungsnummer',
        ])
      ) {
        return createValidationErrorResponse([
          'suchworte` für Volltextsuche',
          'titel` für Titelsuche',
          'bundesland` für Bundesland',
          'bezirksverwaltungsbehoerde` für Bezirksverwaltungsbehörde',
          'kundmachungsnummer` für Kundmachungsnummer',
        ]);
      }
    
      const params = buildBaseParams('Bvb', limit, seite);
      addOptionalParams(params, [
        [suchworte, 'Suchworte'],
        [titel, 'Titel'],
        [bundesland, 'Bundesland'],
        [bezirksverwaltungsbehoerde, 'Bezirksverwaltungsbehoerde'],
        [kundmachungsnummer, 'Kundmachungsnummer'],
        [kundmachungsdatum_von, 'Kundmachungsdatum.Von'],
        [kundmachungsdatum_bis, 'Kundmachungsdatum.Bis'],
        [im_ris_seit, 'ImRisSeit'],
      ]);
    
      return executeSearchTool(searchBezirke, params, response_format);
    },
  • Input parameter schema validation using Zod for the 'ris_bezirke' tool.
    {
      suchworte: z.string().max(1000).optional().describe('Full-text search terms'),
      titel: z.string().max(500).optional().describe('Search in titles'),
      bundesland: BundeslandSchema.optional().describe(
        'Filter by state - Burgenland, Kärnten, Niederösterreich, Oberösterreich, Salzburg, Steiermark, Tirol, Vorarlberg, Wien',
      ),
      bezirksverwaltungsbehoerde: z
        .string()
        .max(200)
        .optional()
        .describe(
          'District authority name (e.g., "Bezirkshauptmannschaft Innsbruck", "Bezirkshauptmannschaft Amstetten")',
        ),
      kundmachungsnummer: z.string().max(100).optional().describe('Announcement number'),
      kundmachungsdatum_von: DateSchema.optional().describe('Announcement date from (YYYY-MM-DD)'),
      kundmachungsdatum_bis: DateSchema.optional().describe('Announcement date to (YYYY-MM-DD)'),
      im_ris_seit: z.enum(IM_RIS_SEIT_VALUES).optional().describe('Filter by time in RIS'),
      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"'),
    },
Behavior3/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 reveals the geographical limitation (only certain states publish here) which is valuable context not in the schema. However, it doesn't describe important behavioral aspects like whether this is a read-only search, what the response format looks like, pagination behavior (implied by page/limit parameters but not explained), or any rate limits/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.

Conciseness4/5

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

The description is well-structured and appropriately sized. It starts with the core purpose, provides usage guidance, adds an important geographical constraint note, and gives concrete examples. Each sentence earns its place, though the example queries could be slightly more concise. The information is front-loaded with the most important details first.

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?

Given 11 parameters, no annotations, and no output schema, the description provides adequate but incomplete context. It covers the purpose and geographical limitations well, but doesn't address the response format (beyond the response_format parameter), pagination behavior, or what constitutes a successful search. For a search tool with many parameters and no output schema, more guidance on result interpretation would be helpful.

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 11 parameters thoroughly. The description adds minimal parameter semantics beyond the schema - it mentions example queries with bundesland and suchworte parameters, but doesn't provide additional meaning or usage guidance for the parameters. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 for 'Austrian district administrative authority announcements (Kundmachungen der Bezirksverwaltungsbehörden)' and provides examples. It specifies the resource type (announcements/ordinances) and geographical scope (district authorities), but doesn't explicitly differentiate from sibling tools like ris_gemeinden or ris_verordnungen that might also search Austrian legal documents.

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 some usage context by stating 'Use this tool to find announcements and ordinances from district administrative authorities' and listing which states publish here. However, it doesn't explicitly say when to use this versus sibling tools like ris_landesrecht or ris_verordnungen that might cover similar content types. The geographical limitation is helpful but not comprehensive guidance on tool selection.

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