Skip to main content
Glama

Reforms

reforms
Read-onlyIdempotent

Trace a Mexican law’s amendment timeline, listing each decree’s number, DOF date, title, PDF, and the git version that carries it.

Instructions

Reform timeline of a law from the LeyesBiblio data in leyes-mx: number, DOF date, title and PDF of each decree, and which version in git carries it (own version, grouped with others, older than the archive, or not consolidated yet).

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

Input Schema

NameRequiredDescriptionDefault
lawYesLaw abbreviation or slug, e.g. 'LFT', 'CPEUM', 'lgsm'. See list_laws.
limitNoMaximum decrees (newest first).
sinceNoOnly decrees published on or after this date.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/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 safety is covered. The description adds real behavioral context beyond them: the underlying data source (LeyesBiblio in leyes-mx) and the four possible git consolidation states (own version, grouped with others, older than the archive, not consolidated), which tells the agent what 'carries it' actually means.

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?

It is a single dense sentence, front-loaded with the resource and immediately followed by the returned fields; nothing is redundant. The nested parenthetical of consolidation states is slightly taxing to parse but every clause carries information.

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 structure, and annotations cover safety and idempotency. It is complete for calling the tool correctly; only the absence of alternative-routing guidance keeps it from a 5.

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%, including the example abbreviations and the 'See list_laws' pointer for 'law', plus the newest-first and date-filter semantics for limit/since. The description adds no parameter-level meaning of its own, so the baseline 3 applies.

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 names a specific resource and scope — the reform/decree timeline of a single law — and enumerates exactly what each entry carries (decree number, DOF date, title, PDF link, and git consolidation status). That field list lets an agent distinguish it from siblings like diff_reform or transitorios without opening a schema.

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: the presence of the required 'law' parameter and the phrase 'timeline of a law' tell the agent this is the per-law decree listing. There is no explicit when-to-use/when-not or routing to diff_reform for comparisons or transitorios for transitory articles, so an agent must infer the boundary itself.

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