Skip to main content
Glama

ris_landesrecht

Search Austrian state laws by keywords, titles, or specific federal states to find relevant legal information from provincial legislation databases.

Instructions

Search Austrian state/provincial laws (Landesrecht).

Use this tool to find laws enacted by Austrian federal states (Bundeslaender).

Example: suchworte="Bauordnung", bundesland="Salzburg"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
suchworteNoFull-text search terms
titelNoSearch in law titles
bundeslandNoFilter by state - Wien, Niederoesterreich, Oberoesterreich, Salzburg, Tirol, Vorarlberg, Kaernten, Steiermark, Burgenland
applikationNo"LrKons" (consolidated, default)LrKons
seiteNoPage number
limitNoResults per page
response_formatNo"markdown" or "json"markdown

Implementation Reference

  • The handler function for the 'ris_landesrecht' tool which processes search parameters and executes the search.
    async (args) => {
      const { suchworte, titel, bundesland, applikation, seite, limit, response_format } = args;
    
      if (!hasAnyParam(args, ['suchworte', 'titel', 'bundesland'])) {
        return createValidationErrorResponse([
          'suchworte` fuer Volltextsuche',
          'titel` fuer Suche in Gesetzesnamen',
          'bundesland` fuer Suche nach Bundesland',
        ]);
      }
    
      const params = buildBaseParams(applikation, limit, seite);
      addOptionalParams(params, [
        [suchworte, 'Suchworte'],
        [titel, 'Titel'],
      ]);
    
      if (bundesland) {
        const apiKey = BUNDESLAND_MAPPING[bundesland];
        if (apiKey) {
          params[`Bundesland.${apiKey}`] = 'true';
        }
      }
    
      return executeSearchTool(searchLandesrecht, params, response_format);
    },
  • Registration of the 'ris_landesrecht' tool with the MCP server.
    export function registerLandesrechtTool(server: McpServer): void {
      server.tool(
        'ris_landesrecht',
        `Search Austrian state/provincial laws (Landesrecht).
    
    Use this tool to find laws enacted by Austrian federal states (Bundeslaender).
    
    Example: suchworte="Bauordnung", bundesland="Salzburg"`,
        {
          suchworte: z.string().max(1000).optional().describe('Full-text search terms'),
          titel: z.string().max(500).optional().describe('Search in law titles'),
          bundesland: LandesrechtBundeslandSchema.optional().describe(
            'Filter by state - Wien, Niederoesterreich, Oberoesterreich, Salzburg, Tirol, Vorarlberg, Kaernten, Steiermark, Burgenland',
          ),
          applikation: z
            .enum(['LrKons'])
            .default('LrKons')
            .describe('"LrKons" (consolidated, default)'),
          seite: z.number().default(1).describe('Page number'),
          limit: z.number().default(20).describe('Results per page'),
          response_format: z
            .enum(['markdown', 'json'])
            .default('markdown')
            .describe('"markdown" or "json"'),
        },
        async (args) => {
          const { suchworte, titel, bundesland, applikation, seite, limit, response_format } = args;
    
          if (!hasAnyParam(args, ['suchworte', 'titel', 'bundesland'])) {
            return createValidationErrorResponse([
              'suchworte` fuer Volltextsuche',
              'titel` fuer Suche in Gesetzesnamen',
              'bundesland` fuer Suche nach Bundesland',
            ]);
          }
    
          const params = buildBaseParams(applikation, limit, seite);
          addOptionalParams(params, [
            [suchworte, 'Suchworte'],
            [titel, 'Titel'],
          ]);
    
          if (bundesland) {
            const apiKey = BUNDESLAND_MAPPING[bundesland];
            if (apiKey) {
              params[`Bundesland.${apiKey}`] = 'true';
            }
          }
    
          return executeSearchTool(searchLandesrecht, params, response_format);
        },
      );
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions searching and filtering, but lacks details on behavioral traits like pagination behavior (implied by 'seite' and 'limit' parameters), rate limits, authentication needs, or what the output looks like (no output schema). It doesn't contradict annotations, but is insufficient for a mutation-less search tool.

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 concise and well-structured: a clear purpose statement, a usage guideline, and an example. Every sentence adds value, with no wasted words. It could be slightly more front-loaded by integrating the example more seamlessly, but overall it's efficient.

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 complexity (7 parameters, no annotations, no output schema), the description is moderately complete. It covers the purpose and basic usage, but lacks details on output format, error handling, or advanced behavioral context. The schema handles parameter documentation well, but the description doesn't fully compensate for missing annotations and output schema.

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 fully documents all 7 parameters. The description adds minimal value beyond the schema: it implies 'suchworte' and 'bundesland' are key parameters via the example, but doesn't explain parameter interactions or semantics not in the schema. Baseline 3 is appropriate as 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's purpose: 'Search Austrian state/provincial laws (Landesrecht).' It specifies the resource (Austrian state laws) and verb (search). However, it doesn't explicitly differentiate from siblings like 'ris_bundesrecht' (federal laws) or 'ris_landesgesetzblatt' (state law gazettes), though the domain is distinct.

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: 'Use this tool to find laws enacted by Austrian federal states (Bundeslaender).' This implies when to use it (for state laws) but doesn't explicitly mention when not to use it or name alternatives among the siblings. The example helps but doesn't offer comparative guidance.

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