Skip to main content
Glama

ris_bundesgesetzblatt

Search Austrian Federal Law Gazettes to find official publications of laws, ordinances, and treaties for historical research and tracking when laws were enacted.

Instructions

Search Austrian Federal Law Gazettes (Bundesgesetzblatt).

Use this tool for historical research and tracking when laws were enacted. Contains official publications of federal laws, ordinances, and treaties.

Example queries:

  • bgblnummer="120", jahrgang="2023", teil="1" -> Find specific gazette

  • suchworte="Klimaschutz" -> Full-text search in gazettes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bgblnummerNoGazette number (e.g., "120")
teilNoPart - "1" (I=Laws), "2" (II=Ordinances), "3" (III=Treaties)
jahrgangNoYear (e.g., "2023")
suchworteNoFull-text search terms
titelNoSearch in gazette titles
applikationNo"BgblAuth" (authentic 2004+, default), "BgblPdf" (PDF), "BgblAlt" (1945-2003)BgblAuth
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 for 'ris_bundesgesetzblatt' tool which validates input parameters, prepares search criteria, and invokes the search client.
    async (args) => {
      const {
        bgblnummer,
        teil,
        jahrgang,
        suchworte,
        titel,
        applikation,
        seite,
        limit,
        response_format,
      } = args;
    
      if (!hasAnyParam(args, ['bgblnummer', 'jahrgang', 'suchworte', 'titel'])) {
        return createValidationErrorResponse([
          'bgblnummer` fuer Gesetzblatt-Nummer',
          'jahrgang` fuer Jahr',
          'suchworte` fuer Volltextsuche',
          'titel` fuer Suche in Titeln',
        ]);
      }
    
      const params = buildBaseParams(applikation, limit, seite);
      addOptionalParams(params, [
        [bgblnummer, 'Bgblnummer'],
        [teil, 'Teil'],
        [jahrgang, 'Jahrgang'],
        [suchworte, 'Suchworte'],
        [titel, 'Titel'],
      ]);
    
      return executeSearchTool(searchBundesrecht, params, response_format);
    },
  • Registration of the 'ris_bundesgesetzblatt' tool within the McpServer instance.
    export function registerBundesgesetzblattTool(server: McpServer): void {
      server.tool(
        'ris_bundesgesetzblatt',
        `Search Austrian Federal Law Gazettes (Bundesgesetzblatt).
    
    Use this tool for historical research and tracking when laws were enacted.
    Contains official publications of federal laws, ordinances, and treaties.
    
    Example queries:
      - bgblnummer="120", jahrgang="2023", teil="1" -> Find specific gazette
      - suchworte="Klimaschutz" -> Full-text search in gazettes`,
        {
          bgblnummer: z.string().max(100).optional().describe('Gazette number (e.g., "120")'),
          teil: z
            .enum(['1', '2', '3'])
            .optional()
            .describe('Part - "1" (I=Laws), "2" (II=Ordinances), "3" (III=Treaties)'),
          jahrgang: z.string().max(10).optional().describe('Year (e.g., "2023")'),
          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(['BgblAuth', 'BgblPdf', 'BgblAlt'])
            .default('BgblAuth')
            .describe('"BgblAuth" (authentic 2004+, default), "BgblPdf" (PDF), "BgblAlt" (1945-2003)'),
          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 {
            bgblnummer,
            teil,
            jahrgang,
            suchworte,
            titel,
            applikation,
            seite,
            limit,
            response_format,
          } = args;
    
          if (!hasAnyParam(args, ['bgblnummer', 'jahrgang', 'suchworte', 'titel'])) {
            return createValidationErrorResponse([
              'bgblnummer` fuer Gesetzblatt-Nummer',
              'jahrgang` fuer Jahr',
              'suchworte` fuer Volltextsuche',
              'titel` fuer Suche in Titeln',
            ]);
          }
    
          const params = buildBaseParams(applikation, limit, seite);
          addOptionalParams(params, [
            [bgblnummer, 'Bgblnummer'],
            [teil, 'Teil'],
            [jahrgang, 'Jahrgang'],
            [suchworte, 'Suchworte'],
            [titel, 'Titel'],
          ]);
    
          return executeSearchTool(searchBundesrecht, params, response_format);
        },
      );
    }
  • Input parameter schema validation for the 'ris_bundesgesetzblatt' tool using Zod.
    {
      bgblnummer: z.string().max(100).optional().describe('Gazette number (e.g., "120")'),
      teil: z
        .enum(['1', '2', '3'])
        .optional()
        .describe('Part - "1" (I=Laws), "2" (II=Ordinances), "3" (III=Treaties)'),
      jahrgang: z.string().max(10).optional().describe('Year (e.g., "2023")'),
      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(['BgblAuth', 'BgblPdf', 'BgblAlt'])
        .default('BgblAuth')
        .describe('"BgblAuth" (authentic 2004+, default), "BgblPdf" (PDF), "BgblAlt" (1945-2003)'),
      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 full burden. It mentions the content scope ('official publications of federal laws, ordinances, and treaties') and provides example queries, but doesn't disclose behavioral aspects like rate limits, authentication requirements, error conditions, or pagination behavior beyond what's in the schema. It adds some context but leaves significant gaps.

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, and includes helpful examples. Every sentence adds value, though the example section could be slightly more concise. Overall efficient with minimal waste.

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?

For a search tool with 9 parameters, 100% schema coverage, but no annotations or output schema, the description provides adequate basic context but lacks important behavioral details. It explains what the tool searches and provides examples, but doesn't cover response format expectations beyond the response_format parameter, error handling, or performance characteristics that would help an agent use it effectively.

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 9 parameters thoroughly. The description provides example queries that illustrate parameter usage (bgblnummer, jahrgang, teil, suchworte) but doesn't add significant semantic meaning beyond what the schema provides. The baseline of 3 is appropriate given the comprehensive schema.

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 Federal Law Gazettes, specifying it's for historical research and tracking law enactment. It distinguishes the resource (Bundesgesetzblatt) but doesn't explicitly differentiate from sibling tools like ris_bundesrecht or ris_landesgesetzblatt, which likely cover related legal materials.

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 ('historical research and tracking when laws were enacted') and example queries, but doesn't explicitly state when to use this tool versus alternatives like ris_bundesrecht or ris_landesgesetzblatt. The guidance is helpful but incomplete for sibling 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