Skip to main content
Glama

ris_landesgesetzblatt

Search official Austrian state law gazettes (Landesgesetzblatt) to find provincial legislation across all 9 federal states using gazette numbers, years, states, or keywords.

Instructions

Search Austrian State Law Gazettes (Landesgesetzblatt).

Use this tool to find official publications of state/provincial laws. Covers all 9 federal states (Bundeslaender).

Example queries:

  • lgblnummer="50", jahrgang="2023", bundesland="Wien"

  • suchworte="Bauordnung", bundesland="Salzburg"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lgblnummerNoGazette number (e.g., "50")
jahrgangNoYear (e.g., "2023")
bundeslandNoFilter by state - Wien, Niederoesterreich, Oberoesterreich, Salzburg, Tirol, Vorarlberg, Kaernten, Steiermark, Burgenland
suchworteNoFull-text search terms
titelNoSearch in gazette titles
applikationNo"LgblAuth" (authentic, default), "Lgbl" (general), "LgblNO" (Lower Austria)LgblAuth
seiteNoPage number (default: 1)
limitNoResults per page 10/20/50/100 (default: 20)
response_formatNo"markdown" (default) or "json"markdown

Implementation Reference

  • The handler function that processes the arguments, validates input, prepares parameters, and executes the search using `executeSearchTool`.
    async (args) => {
      const {
        lgblnummer,
        jahrgang,
        bundesland,
        suchworte,
        titel,
        applikation,
        seite,
        limit,
        response_format,
      } = args;
    
      if (!hasAnyParam(args, ['lgblnummer', 'jahrgang', 'bundesland', 'suchworte', 'titel'])) {
        return createValidationErrorResponse([
          'lgblnummer` fuer Gesetzblatt-Nummer',
          'jahrgang` fuer Jahr',
          'bundesland` fuer Bundesland',
          'suchworte` fuer Volltextsuche',
          'titel` fuer Suche in Titeln',
        ]);
      }
    
      const params = buildBaseParams(applikation, limit, seite);
      addOptionalParams(params, [
        [lgblnummer, 'Lgblnummer'],
        [jahrgang, 'Jahrgang'],
        [suchworte, 'Suchworte'],
        [titel, 'Titel'],
      ]);
    
      if (bundesland) {
        const apiKey = BUNDESLAND_MAPPING[bundesland];
        if (apiKey) {
          params[`Bundesland.${apiKey}`] = 'true';
        }
      }
    
      return executeSearchTool(searchLandesrecht, params, response_format);
    },
  • The registration function `registerLandesgesetzblattTool` which registers the `ris_landesgesetzblatt` tool with the MCP server.
    export function registerLandesgesetzblattTool(server: McpServer): void {
      server.tool(
        'ris_landesgesetzblatt',
        `Search Austrian State Law Gazettes (Landesgesetzblatt).
    
    Use this tool to find official publications of state/provincial laws.
    Covers all 9 federal states (Bundeslaender).
    
    Example queries:
      - lgblnummer="50", jahrgang="2023", bundesland="Wien"
      - suchworte="Bauordnung", bundesland="Salzburg"`,
        {
          lgblnummer: z.string().max(100).optional().describe('Gazette number (e.g., "50")'),
          jahrgang: z.string().max(10).optional().describe('Year (e.g., "2023")'),
          bundesland: LandesrechtBundeslandSchema.optional().describe(
            'Filter by state - Wien, Niederoesterreich, Oberoesterreich, Salzburg, Tirol, Vorarlberg, Kaernten, Steiermark, Burgenland',
          ),
          suchworte: z.string().max(1000).optional().describe('Full-text search terms'),
          titel: z.string().max(500).optional().describe('Search in gazette titles'),
          applikation: z
            .enum(['LgblAuth', 'Lgbl', 'LgblNO'])
            .default('LgblAuth')
            .describe('"LgblAuth" (authentic, default), "Lgbl" (general), "LgblNO" (Lower Austria)'),
          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 {
            lgblnummer,
            jahrgang,
            bundesland,
            suchworte,
            titel,
            applikation,
            seite,
            limit,
            response_format,
          } = args;
    
          if (!hasAnyParam(args, ['lgblnummer', 'jahrgang', 'bundesland', 'suchworte', 'titel'])) {
            return createValidationErrorResponse([
              'lgblnummer` fuer Gesetzblatt-Nummer',
              'jahrgang` fuer Jahr',
              'bundesland` fuer Bundesland',
              'suchworte` fuer Volltextsuche',
              'titel` fuer Suche in Titeln',
            ]);
          }
    
          const params = buildBaseParams(applikation, limit, seite);
          addOptionalParams(params, [
            [lgblnummer, 'Lgblnummer'],
            [jahrgang, 'Jahrgang'],
            [suchworte, 'Suchworte'],
            [titel, 'Titel'],
          ]);
    
          if (bundesland) {
            const apiKey = BUNDESLAND_MAPPING[bundesland];
            if (apiKey) {
              params[`Bundesland.${apiKey}`] = 'true';
            }
          }
    
          return executeSearchTool(searchLandesrecht, params, response_format);
        },
      );
    }
  • Zod schema defining the input parameters for the `ris_landesgesetzblatt` tool.
    {
      lgblnummer: z.string().max(100).optional().describe('Gazette number (e.g., "50")'),
      jahrgang: z.string().max(10).optional().describe('Year (e.g., "2023")'),
      bundesland: LandesrechtBundeslandSchema.optional().describe(
        'Filter by state - Wien, Niederoesterreich, Oberoesterreich, Salzburg, Tirol, Vorarlberg, Kaernten, Steiermark, Burgenland',
      ),
      suchworte: z.string().max(1000).optional().describe('Full-text search terms'),
      titel: z.string().max(500).optional().describe('Search in gazette titles'),
      applikation: z
        .enum(['LgblAuth', 'Lgbl', 'LgblNO'])
        .default('LgblAuth')
        .describe('"LgblAuth" (authentic, default), "Lgbl" (general), "LgblNO" (Lower Austria)'),
      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 states this is a search tool (implying read-only, non-destructive behavior) and mentions it covers all 9 states, but doesn't address authentication needs, rate limits, pagination behavior (beyond parameter descriptions), or what the search results look like. For a search tool with 9 parameters and no annotations, more behavioral context would be helpful.

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 and concise. The first sentence states the purpose, the second provides usage guidance, and the third defines scope. The example queries are directly relevant and illustrative. Every sentence earns its place with no wasted words.

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 the tool's complexity (9 parameters, search functionality) and lack of both annotations and output schema, the description is adequate but incomplete. It explains what the tool does and provides examples, but doesn't describe the return format, result structure, or error conditions. For a search tool with this many parameters, more contextual information would be beneficial.

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 minimal value beyond the schema: it provides two example queries that demonstrate parameter combinations, but doesn't explain parameter semantics beyond what's in the schema descriptions. This meets the baseline for high schema coverage.

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 Law Gazettes (Landesgesetzblatt).' It specifies the exact resource (state law gazettes) and verb (search), and distinguishes it from siblings like ris_bundesgesetzblatt (federal gazettes) and ris_landesrecht (state laws generally). The scope is well-defined: 'Covers all 9 federal states (Bundeslaender).'

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 clear context for when to use this tool: 'Use this tool to find official publications of state/provincial laws.' It implicitly distinguishes from siblings by focusing on gazettes rather than laws themselves (ris_landesrecht) or federal publications (ris_bundesgesetzblatt). However, it doesn't explicitly state when NOT to use it or name specific alternatives, which prevents a perfect score.

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