Skip to main content
Glama

get_article_history

Read-only

Retrieve the complete amendment history of EU regulation articles, including dates and change summaries, to track legislative evolution.

Instructions

Get the full version timeline for a specific article, showing all amendments with dates and change summaries. Premium feature — requires Ansvar Intelligence Portal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regulationYesRegulation ID (e.g., "NIS2", "DORA", "GDPR")
articleYesArticle number (e.g., "21", "6")

Implementation Reference

  • Implementation of the getArticleHistory tool handler.
    export async function getArticleHistory(
      db: DatabaseAdapter,
      input: GetArticleHistoryInput,
    ): Promise<ArticleHistory | { premium: false; message: string }> {
      if (!isPremiumEnabled()) {
        return { premium: false, message: PREMIUM_UPGRADE_MESSAGE };
      }
    
      if (!(await hasVersionsTable(db))) {
        throw new Error('Version tracking data not available in this database build.');
      }
    
      const { regulation, article } = input;
    
      // Find the parent article
      const articleResult = await db.query<{ rowid: number }>(
        'SELECT rowid FROM articles WHERE regulation = $1 AND article_number = $2',
        [regulation, article],
      );
    
      if (articleResult.rows.length === 0) {
        throw new Error(`Article ${article} not found in ${regulation}`);
      }
    
      const articleId = articleResult.rows[0].rowid;
    
      const versions = await db.query<{
        effective_date: string | null;
        superseded_date: string | null;
        change_summary: string | null;
        source_url: string | null;
      }>(
        `SELECT effective_date, superseded_date, change_summary, source_url
         FROM article_versions
         WHERE article_id = $1
         ORDER BY effective_date ASC`,
        [articleId],
      );
    
      const currentVersion =
        versions.rows.length > 0
          ? versions.rows[versions.rows.length - 1].effective_date
          : null;
    
      return {
        regulation,
        article,
        current_version: currentVersion,
        versions: versions.rows,
      };
    }
  • Input type definition for getArticleHistory.
    export interface GetArticleHistoryInput {
      regulation: string;
      article: string;
    }
Behavior4/5

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

Annotations declare readOnlyHint=true, confirming safe read operation. Description adds crucial behavioral context not in annotations: the premium/auth requirement and specific output format (amendments with dates and change summaries). No contradictions with annotations.

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?

Two sentences with zero waste: first sentence front-loads purpose and output description, second states the critical premium constraint. Every word earns its place; no redundant repetition of annotations or schema details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple 2-parameter read tool with full schema coverage, the description adequately compensates for missing output schema by describing return contents (amendments, dates, summaries) and notes the premium restriction. Could enhance by mentioning pagination or volume limits for articles with extensive histories.

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?

Input schema has 100% description coverage (regulation and article parameters fully documented). Description implies targeting a 'specific article' but does not elaborate on parameter formats beyond the schema, which satisfies the baseline for high-coverage schemas.

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?

Description uses specific verb 'Get' with resource 'full version timeline' and clarifies scope with 'showing all amendments with dates and change summaries.' Distinguishes from sibling get_article (current state) by emphasizing historical timeline and from diff_article by offering complete chronology rather than comparison.

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?

Provides prerequisite context with 'Premium feature — requires Ansvar Intelligence Portal,' indicating auth/licensing constraints. However, lacks explicit guidance on when to choose this over get_article (current text) or get_recent_changes (cross-regulation updates), requiring the agent to infer from 'full version timeline.'

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/Ansvar-Systems/eu-regulations'

If you have feedback or need assistance with the MCP directory API, please join our Discord server