Skip to main content
Glama

Biblioteca fiscal de Cumplida · edición abierta (gratuita)

Ley vigente al día del hecho

normativa_vigente
Read-onlyIdempotent

Busca la ley fiscal mexicana vigente en una fecha, por tema o por referencia: leyes federales, reglamentos, RMF y anexos, RGCE, seguridad social, antilavado, estímulos y tratados; sólo versiones aprobadas, con su publicación en el DOF. Ej.: «plazo para concluir una visita domiciliaria», «CFF 46-A», «RMF 2.7.1.21». Sin fecha ni periodo, la ley de hoy, o la de la fecha que nombre la consulta: un año suelto es ese ejercicio («tasa de recargos 2027», el 1 de enero de 2027, con lo ya publicado para él). Cada resultado trae un tramo, su version_id y su fuente oficial: para leerla completa, leer_disposicion con su version_id. Dice si puede haber más resultados (limite, hasta 10). Búsqueda por texto (sin vectores): una consulta que no está en español no se busca y se dice cómo pedirla. Para lo que cambió una reforma o un DOF («reforma fiscal 2027»), que_publico_el_dof. [EN: Mexican tax law in force on a date.]

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": {
      "consulta": "<consulta>"
    },
    "name": "normativa_vigente"
  }
}

Input Schema

NameRequiredDescriptionDefault
fechaNoUn día exacto (AAAA-MM-DD): manda sobre el periodo.
limiteNoCuántos resultados (1 a 10; por omisión, 8).
periodoNoEl periodo del hecho: AAAA-MM o AAAA. Se toma su último día (u hoy si sigue en curso; si aún no empieza, su primer día: la ley ya publicada para él).
consultaYesEl tema en palabras o la referencia («CFF 42», «art. 27 LISR», «regla 3.13.4»).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / periodo / description
      Previous value: -"El periodo del hecho: AAAA-MM o AAAA. Se toma su último día (u hoy si sigue en curso)."New value: +"El periodo del hecho: AAAA-MM o AAAA. Se toma su último día (u hoy si sigue en curso; si aún no empieza, su primer día: la ley ya publicada para él)."
  2. Changed1 schema field changed
    • addedInput schema / properties / limite / description
      Added value: +"Cuántos resultados (1 a 10; por omisión, 8)."
  3. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive and a closed corpus, so the safety profile is covered. The description adds real context beyond that: only approved versions, DOF publication included, default-to-today behavior, bare-year semantics, plain text search without vectors, and a capped result set with a flag for truncation. It does not cover empty-result or error behavior, but the behavioral layer is substantially richer than the annotations alone.

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?

Purpose and corpus are front-loaded, then defaults, return shape, and alternatives in a logical order. The single dense paragraph with nested parentheticals and a trailing English gloss makes it harder to scan than it needs to be, but little of the content is wasted.

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?

With no output schema, the description still explains the return shape (a tramo, its version_id, its official source) and how to continue from it, plus default-date behavior and the result cap. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by explaining the precedence logic concretely, e.g. a lone year means that ejercicio as of January 1 with only what was already published. The limite cap of 10 is restated and tied to the "may be more results" signal, which the schema does not connect to output meaning.

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?

Opens with a specific verb and resource ("Busca la ley fiscal mexicana vigente") and enumerates the corpus covered (federales, reglamentos, RMF y anexos, RGCE, seguridad social, antilavado, estímulos, tratados), with three concrete query examples. It also names the sibling it is not: full-text reading goes to leer_disposicion and reform/DOF questions go to que_publico_el_dof.

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?

Explicit routing rules are given for each alternative: leer_disposicion for the complete text using the returned version_id, que_publico_el_dof for what a reform changed. It also states the default date behavior when fecha/periodo are omitted and that non-Spanish queries are not searched, so the agent knows the boundaries of use.

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