Skip to main content
Glama

Diff Reform

diff_reform
Read-onlyIdempotent

Compare a Mexican law before and after a reform date to list modified, added, or removed articles, new transitional provisions, headings, and article diffs.

Instructions

What a reform changed in a law: every article modified, added or removed between the version before and the version that carries the reform, new transitorios and headings, and the diffs. When the archive groups several reforms in one version, articles whose editorial note cites this reform date are listed first.

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>",
      "reform_date": "<reform_date>"
    },
    "name": "diff_reform"
  }
}

Input Schema

NameRequiredDescriptionDefault
lawYesLaw abbreviation or slug, e.g. 'LFT', 'CPEUM', 'lgsm'. See list_laws.
modeNo'words' or 'unified'.words
limitNoMaximum number of article diffs to return.
offsetNoSkip this many changed articles.
reform_dateYesDOF publication date of the reform decree (YYYY-MM-DD).

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 establish readOnly, idempotent, closed-world behavior, so the bar is lower, yet the description adds real value: it discloses the exact result contents (modified, added, removed articles, new transitorios and headings) and a non-obvious ordering rule where articles whose editorial note cites this reform date are listed first when several reforms share a version. It does not cover empty-result behavior or how mode affects output, but the ordering rule is genuinely useful context unavailable elsewhere.

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 dense sentences, front-loaded with the core purpose and followed by the ordering caveat; nothing is wasted. The first sentence is heavy with enumerated return elements but each earns its place by defining scope.

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?

With an output schema present, the description need not explain return shape, and it still characterizes contents and ordering. Minor gaps remain around pagination semantics given limit/offset defaults and what happens when a reform date matches nothing or is not a reform date.

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% and every parameter (law, mode, limit, offset, reform_date) is documented in the schema, including the enum and bounds. The description adds only indirect meaning ('cites this reform date'), so the baseline of 3 applies.

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 names a specific verb and resource: it reports what a reform changed in a law, enumerating modified/added/removed articles plus new transitorios, headings and the diffs. That scope implicitly separates it from per-article tools like diff_article or article_history, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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 implied by the framing ('what a reform changed'), so an agent can infer this is the per-reform, whole-law diff as opposed to a single-article lookup. There is no explicit when-to-use/when-not-to-use guidance and no named alternative such as diff_article for single-article inspection.

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