Skip to main content
Glama

Biblioteca abierta de Cumplida

Qué cambió en la norma

que_cambio_en_la_norma
Read-onlyIdempotent

Qué cambió en una disposición de la ley, la RMF o un anexo («CFF 42», «regla 2.7.1.21»): la versión que regía en fecha (sin ella, la más reciente) contra la anterior, con la publicación del DOF de cada una, sus vigencias y lo que cambió, literal de la biblioteca (sólo versiones aprobadas): el párrafo casi igual, marcado por palabra; el que salió o entró, entero. Si dicen lo mismo, cuándo cambió su texto por última vez. Lista todas sus versiones con su version_id (para ir a otra, pase una fecha dentro de su vigencia). Para citar, leer_disposicion con el version_id. Para todo lo que cambió una reforma o un DOF de una vez («reforma fiscal 2027», una nota del DOF), que_publico_el_dof.

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": {
      "referencia": "<referencia>"
    },
    "name": "que_cambio_en_la_norma"
  }
}

Input Schema

NameRequiredDescriptionDefault
fechaNoUn día (AAAA-MM-DD) dentro de la vigencia de la versión que se quiere comparar con su anterior. Sin ella, la más reciente.
periodoNoO el periodo (AAAA o AAAA-MM) de la versión que se quiere comparar: su último día (u hoy si sigue en curso; si aún no empieza, su primer día). `fecha` manda.
referenciaYesLa disposición: «CFF 42», «art. 27 LISR», «regla 2.7.1.21».

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / periodo
      Added value: +{
      +  "description": "O el periodo (AAAA o AAAA-MM) de la versión que se quiere comparar: su último día (u hoy si sigue en curso; si aún no empieza, su primer día). `fecha` manda.",
      +  "pattern": "^20\\d{2}(?:-(?:0[1-9]|1[0-2]))?$",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / fecha / description
      Added value: +"Un día (AAAA-MM-DD) dentro de la vigencia de la versión que se quiere comparar con su anterior. Sin ella, la más reciente."
    • addedInput schema / properties / referencia / description
      Added value: +"La disposición: «CFF 42», «art. 27 LISR», «regla 2.7.1.21»."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the library scope (sólo versiones aprobadas), the exact diff granularity (word-marked near-identical paragraphs, whole paragraphs added or removed), and that the response includes DOF publication and vigencias plus a list of all versions with version_id. The one gap is pagination/size behavior for long paragraph-level diffs, which is not mentioned.

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?

Content is front-loaded and every clause carries information (scope, diff detail, output fields, alternatives), but it is delivered as one very dense run-on sentence with stacked parentheticals, which costs readability. Trimming or splitting the parentheticals would improve it without losing substance.

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

Completeness5/5

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

For a version-comparison tool with no output schema and only thin annotations, the description covers what is compared, how differences are represented, what metadata accompanies them, what happens when nothing changed, and how to move between versions. An agent has everything needed to call it and interpret the result.

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 coverage is 100% and the schema already explains fecha, periodo and referencia precisely, including that `fecha` manda over `periodo`. The description adds little beyond it aside from the practical hint that to reach another version you pass a `fecha` inside its vigencia, so baseline 3 is right.

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?

States a specific verb and resource — qué cambió en una disposición de la ley, la RMF o un anexo — with concrete reference examples («CFF 42», «regla 2.7.1.21») and distinguishes itself from siblings by name (leer_disposicion, que_publico_el_dof). An agent can identify the tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use leer_disposicion with version_id to cite, and que_publico_el_dof for everything a whole reform or DOF publication changed at once. It also states the fallback behavior when versions are identical (returns when the text last changed), so the agent knows the outcome of edge cases.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources