Skip to main content
Glama

ris_history

Track changes to Austrian legal documents over time, showing creation, modification, and deletion dates across federal, state, judicial, and other legal applications.

Instructions

Search document change history (Aenderungshistorie).

Use this tool to track changes to legal documents over time. Shows when documents were created, modified, or deleted.

Available applications (30 total):

  • Bundesrecht: Bundesnormen, BgblAuth, BgblAlt, BgblPdf, RegV

  • Landesrecht: Landesnormen, LgblAuth, Lgbl, LgblNO, Vbl, Gemeinderecht, GemeinderechtAuth

  • Judikatur: Justiz, Vfgh, Vwgh, Bvwg, Lvwg, Dsk, Gbk, Pvak, AsylGH

  • Sonstige: Bvb, Mrp, Erlaesse, PruefGewO, Avsv, Spg, KmGer, Dok, Normenliste

Example queries:

  • applikation="Bundesnormen", aenderungen_von="2024-01-01", aenderungen_bis="2024-01-31"

  • applikation="Justiz", aenderungen_von="2024-06-01"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applikationYesApplication to search history for - categories: Bundesrecht (Bundesnormen, BgblAuth, BgblAlt, BgblPdf, RegV), Landesrecht (Landesnormen, LgblAuth, Lgbl, LgblNO, Vbl, Gemeinderecht), Judikatur (Justiz, Vfgh, Vwgh, Bvwg, Lvwg, Dsk, Gbk, Pvak, AsylGH), Sonstige (Bvb, Mrp, Erlaesse, PruefGewO, Avsv, Spg, KmGer, Dok, Normenliste)
aenderungen_vonNoChanges from date (YYYY-MM-DD)
aenderungen_bisNoChanges to date (YYYY-MM-DD)
include_deletedNoInclude deleted documents in results (default: false)
seiteNoPage number (default: 1)
limitNoResults per page 10/20/50/100 (default: 20)
response_formatNo"markdown" (default) or "json"markdown

Implementation Reference

  • The async handler function for the ris_history tool. It constructs the parameters and calls `executeSearchTool` using `searchHistory`.
    async (args) => {
      const {
        applikation,
        aenderungen_von,
        aenderungen_bis,
        include_deleted,
        seite,
        limit,
        response_format,
      } = args;
    
      if (!hasAnyParam(args, ['aenderungen_von', 'aenderungen_bis'])) {
        return createValidationErrorResponse([
          'aenderungen_von` fuer Aenderungen ab Datum',
          'aenderungen_bis` fuer Aenderungen bis Datum',
        ]);
      }
    
      // Note: History endpoint uses "Anwendung" not "Applikation"
      const params: Record<string, unknown> = {
        Anwendung: applikation,
        DokumenteProSeite: limitToDokumenteProSeite(limit),
        Seitennummer: seite,
      };
    
      addOptionalParams(params, [
        [aenderungen_von, 'AenderungenVon'],
        [aenderungen_bis, 'AenderungenBis'],
      ]);
      if (include_deleted) params['IncludeDeletedDocuments'] = 'true';
    
      return executeSearchTool(searchHistory, params, response_format);
    },
  • The registration of the ris_history tool within the MCP server using `registerHistoryTool`.
    export function registerHistoryTool(server: McpServer): void {
      server.tool(
        'ris_history',
        `Search document change history (Aenderungshistorie).
    
    Use this tool to track changes to legal documents over time.
    Shows when documents were created, modified, or deleted.
    
    Available applications (30 total):
      - Bundesrecht: Bundesnormen, BgblAuth, BgblAlt, BgblPdf, RegV
      - Landesrecht: Landesnormen, LgblAuth, Lgbl, LgblNO, Vbl, Gemeinderecht, GemeinderechtAuth
      - Judikatur: Justiz, Vfgh, Vwgh, Bvwg, Lvwg, Dsk, Gbk, Pvak, AsylGH
      - Sonstige: Bvb, Mrp, Erlaesse, PruefGewO, Avsv, Spg, KmGer, Dok, Normenliste
    
    Example queries:
      - applikation="Bundesnormen", aenderungen_von="2024-01-01", aenderungen_bis="2024-01-31"
      - applikation="Justiz", aenderungen_von="2024-06-01"`,
        {
          applikation: z
            .enum(VALID_HISTORY_APPLICATIONS)
            .describe(
              'Application to search history for - categories: Bundesrecht (Bundesnormen, BgblAuth, BgblAlt, BgblPdf, RegV), ' +
                'Landesrecht (Landesnormen, LgblAuth, Lgbl, LgblNO, Vbl, Gemeinderecht), ' +
                'Judikatur (Justiz, Vfgh, Vwgh, Bvwg, Lvwg, Dsk, Gbk, Pvak, AsylGH), ' +
                'Sonstige (Bvb, Mrp, Erlaesse, PruefGewO, Avsv, Spg, KmGer, Dok, Normenliste)',
            ),
          aenderungen_von: DateSchema.optional().describe('Changes from date (YYYY-MM-DD)'),
          aenderungen_bis: DateSchema.optional().describe('Changes to date (YYYY-MM-DD)'),
          include_deleted: z
            .boolean()
            .default(false)
            .describe('Include deleted documents in results (default: false)'),
          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 {
            applikation,
            aenderungen_von,
            aenderungen_bis,
            include_deleted,
            seite,
            limit,
            response_format,
          } = args;
    
          if (!hasAnyParam(args, ['aenderungen_von', 'aenderungen_bis'])) {
            return createValidationErrorResponse([
              'aenderungen_von` fuer Aenderungen ab Datum',
              'aenderungen_bis` fuer Aenderungen bis Datum',
            ]);
          }
    
          // Note: History endpoint uses "Anwendung" not "Applikation"
          const params: Record<string, unknown> = {
            Anwendung: applikation,
            DokumenteProSeite: limitToDokumenteProSeite(limit),
            Seitennummer: seite,
          };
    
          addOptionalParams(params, [
            [aenderungen_von, 'AenderungenVon'],
            [aenderungen_bis, 'AenderungenBis'],
          ]);
          if (include_deleted) params['IncludeDeletedDocuments'] = 'true';
    
          return executeSearchTool(searchHistory, 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. It explains what the tool does (search change history) and provides example queries, but doesn't disclose important behavioral aspects like pagination behavior (implied by page/limit parameters), rate limits, authentication requirements, or what the response format looks like beyond the response_format parameter.

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 with a clear purpose statement, usage guidance, categorized application list, and example queries. While comprehensive, it could be more concise by reducing the full application list repetition (already in schema) or integrating the categories more tightly with the purpose statement.

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 7-parameter search tool with no annotations and no output schema, the description provides good purpose and parameter context but lacks critical information about response structure, error conditions, and operational constraints. The example queries help but don't fully compensate for the missing output documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 value by grouping the 30 applications into 4 categories (Bundesrecht, Landesrecht, Judikatur, Sonstige) and providing concrete example queries that demonstrate parameter usage patterns, which helps users understand how to combine parameters effectively.

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 searching document change history for legal documents, specifying it tracks creation, modification, and deletion events. It distinguishes itself from siblings by focusing on historical changes rather than current document retrieval or other legal data access.

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 track changes to legal documents over time') and lists 30 specific applications/categories. However, it doesn't explicitly state when NOT to use it or name alternative tools for similar purposes among the siblings.

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