Skip to main content
Glama

ris_bundesrecht

Search Austrian federal laws and legislation by keywords, titles, or specific paragraphs to find legal information from official sources.

Instructions

Search Austrian federal laws (Bundesrecht).

Use this tool to find Austrian federal legislation like ABGB, StGB, UGB, etc.

Example queries:

  • suchworte="Mietrecht" -> Find laws mentioning rent law

  • titel="ABGB", paragraph="1319a" -> Find specific ABGB section

  • applikation="Begut" -> Search draft legislation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
suchworteNoFull-text search terms (e.g., "Mietrecht", "Schadenersatz")
titelNoSearch in law titles (e.g., "ABGB", "Strafgesetzbuch")
paragraphNoParagraph number to search for (e.g., "1295" for §1295)
applikationNoData source - "BrKons" (consolidated, default), "Begut" (drafts), "BgblAuth" (gazette), "Erv" (English)BrKons
fassung_vomNoDate for historical version (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

  • The handler function for the `ris_bundesrecht` tool. It processes the arguments, prepares the search parameters, and delegates the execution to `executeSearchTool`.
    async (args) => {
      const {
        suchworte,
        titel,
        paragraph,
        applikation,
        fassung_vom,
        seite,
        limit,
        response_format,
      } = args;
    
      if (!hasAnyParam(args, ['suchworte', 'titel', 'paragraph'])) {
        return createValidationErrorResponse([
          'suchworte` fuer Volltextsuche',
          'titel` fuer Suche in Gesetzesnamen',
          'paragraph` fuer Suche nach Paragraphen',
        ]);
      }
    
      const params = buildBaseParams(applikation, limit, seite);
      addOptionalParams(params, [
        [suchworte, 'Suchworte'],
        [titel, 'Titel'],
        [fassung_vom, 'FassungVom'],
      ]);
    
      if (paragraph) {
        params['Abschnitt.Von'] = paragraph;
        params['Abschnitt.Bis'] = paragraph;
        params['Abschnitt.Typ'] = 'Paragraph';
      }
    
      return executeSearchTool(searchBundesrecht, params, response_format);
    },
  • The registration function for the `ris_bundesrecht` tool. It defines the tool name, description, schema, and handler.
    export function registerBundesrechtTool(server: McpServer): void {
      server.tool(
        'ris_bundesrecht',
        `Search Austrian federal laws (Bundesrecht).
    
    Use this tool to find Austrian federal legislation like ABGB, StGB, UGB, etc.
    
    Example queries:
      - suchworte="Mietrecht" -> Find laws mentioning rent law
      - titel="ABGB", paragraph="1319a" -> Find specific ABGB section
      - applikation="Begut" -> Search draft legislation`,
        {
          suchworte: z
            .string()
            .max(1000)
            .optional()
            .describe('Full-text search terms (e.g., "Mietrecht", "Schadenersatz")'),
          titel: z
            .string()
            .max(500)
            .optional()
            .describe('Search in law titles (e.g., "ABGB", "Strafgesetzbuch")'),
          paragraph: z
            .string()
            .max(100)
            .optional()
            .describe('Paragraph number to search for (e.g., "1295" for §1295)'),
          applikation: BundesrechtApplikationSchema.default('BrKons').describe(
            'Data source - "BrKons" (consolidated, default), "Begut" (drafts), "BgblAuth" (gazette), "Erv" (English)',
          ),
          fassung_vom: DateSchema.optional().describe('Date for historical version (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,
            paragraph,
            applikation,
            fassung_vom,
            seite,
            limit,
            response_format,
          } = args;
    
          if (!hasAnyParam(args, ['suchworte', 'titel', 'paragraph'])) {
            return createValidationErrorResponse([
              'suchworte` fuer Volltextsuche',
              'titel` fuer Suche in Gesetzesnamen',
              'paragraph` fuer Suche nach Paragraphen',
            ]);
          }
    
          const params = buildBaseParams(applikation, limit, seite);
          addOptionalParams(params, [
            [suchworte, 'Suchworte'],
            [titel, 'Titel'],
            [fassung_vom, 'FassungVom'],
          ]);
    
          if (paragraph) {
            params['Abschnitt.Von'] = paragraph;
            params['Abschnitt.Bis'] = paragraph;
            params['Abschnitt.Typ'] = 'Paragraph';
          }
    
          return executeSearchTool(searchBundesrecht, params, response_format);
        },
      );
    }
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 describes the search functionality and provides example use cases, but doesn't mention important behavioral aspects like pagination behavior (implied by page/limit parameters), rate limits, authentication requirements, or what happens when no results are found. The examples help but don't constitute full behavioral transparency.

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 - a clear purpose statement, a usage directive, and three specific example queries that demonstrate different parameter combinations. Every sentence earns its place with zero wasted words, and the information is front-loaded appropriately.

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 8 parameters, 100% schema coverage, but no annotations and no output schema, the description is adequate but has gaps. It explains what the tool does and provides usage examples, but doesn't describe the return format, error conditions, or result structure. The examples help bridge some gaps, but more complete behavioral context 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?

With 100% schema description coverage, the baseline is 3. The description adds some value through the example queries that show how parameters can be combined (e.g., titel='ABGB', paragraph='1319a'), but doesn't provide additional semantic context beyond what's already well-documented in the schema 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's purpose as 'Search Austrian federal laws (Bundesrecht)' and provides specific examples of legislation types (ABGB, StGB, UGB). It distinguishes this tool from siblings like ris_landesrecht (state laws) and ris_judikatur (case law) by focusing specifically on federal legislation.

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 ('to find Austrian federal legislation') and includes helpful example queries showing different search approaches. However, it doesn't explicitly state when NOT to use this tool or mention specific alternatives among the sibling tools for different types of legal content.

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