Skip to main content
Glama

Article History

article_history
Read-onlyIdempotent

Tracks every archived change to a Mexican federal law article—added, modified, repealed, or removed—with DOF date, commit, and decree for each reform.

Instructions

Every change to one article across the archived versions: when it was added, modified, repealed or removed, with the DOF date, commit and decree of each change. In versions that group several reforms, the Cámara's editorial note tells which decree touched it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "law": "<law>",
      "article": "<article>"
    },
    "name": "article_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
lawYesLaw abbreviation or slug, e.g. 'LFT', 'CPEUM', 'lgsm'. See list_laws.
articleYesArticle number as written in the law: '27', '1o', '3o. Bis', '15-A', '353-Ñ', '29-A Bis', '21 bis 1'. Extra words such as 'fracción IV' are ignored.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description adds genuine value beyond that: it enumerates the per-change payload (DOF date, commit, decree) and explains a non-obvious nuance — that in versions grouping several reforms, the Cámara's editorial note identifies which decree touched the article. It stops short of describing ordering, pagination, or what happens for an article with no recorded changes.

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?

Two sentences, front-loaded with the core scope before the editorial-note caveat. Every clause carries information; the only mild looseness is the enumerative 'with the DOF date, commit and decree' phrasing, which could be tightened without losing meaning.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile; parameters are fully documented in the schema. The description supplies the one thing structured fields cannot — the semantics of the historical record and the grouped-reform caveat. The remaining gap is guidance on how this relates to the diff/reforms siblings.

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%: both `law` and `article` are documented with formats, examples and normalization rules ('fracción IV' ignored). The description adds no parameter-level information, so the baseline of 3 applies — the schema does all the work here.

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 states a specific resource and scope: 'every change to one article across the archived versions', enumerating the change types (added, modified, repealed, removed) and the metadata returned (DOF date, commit, decree). This is clearly a per-article timeline tool rather than a diff or full-text fetch. It does not name or contrast with siblings such as diff_article or reforms, so the differentiation is left implicit.

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?

Usage is only implied by the scope wording: an agent can infer this is for tracing the historical sequence of changes to a single article. There is no explicit 'use this when...' clause, no statement of when to prefer diff_article or reforms instead, and no stated prerequisites (e.g., law must exist in list_laws).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.