Skip to main content
Glama

Biblioteca abierta de Cumplida

Qué publicó el DOF y qué cambió

que_publico_el_dof
Read-onlyIdempotent

Qué publicó el Diario Oficial de la Federación y qué cambió con cada decreto, de una vez: por codigo_dof (la nota del DOF, «5803757»), por día de publicación (fecha; con hasta, un rango), por ordenamiento («LISR», «LIF», «CFF») o por palabras («reforma fiscal 2027», «Ley de Ingresos 2027»). Por decreto: título, fecha y liga al DOF, y cada disposición con texto aprobado: si es reforma, adición, derogación o texto nuevo, desde cuándo rige (y si rige después que el resto del decreto) y la llamada siguiente (leer_disposicion con su version_id; que_cambio_en_la_norma con su referencia y fecha). Lo que la biblioteca sigue cotejando contra el DOF no se muestra. Dice cuántos hay y cómo pedir el resto (pagina).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "que_publico_el_dof"
  }
}

Input Schema

NameRequiredDescriptionDefault
fechaNoEl día de publicación en el DOF (AAAA-MM-DD); con `hasta`, desde ese día.
hastaNoEl último día de publicación del rango (AAAA-MM-DD).
paginaNoCon varias publicaciones, la página de 4 publicaciones; con una sola, la de 40 disposiciones. Por omisión, 1.
consultaNoPalabras: «reforma fiscal 2027» (el paquete de ese ejercicio), «Ley de Ingresos 2027», «LISR 2027», «13 de noviembre de 2026».
codigo_dofNoLa nota del DOF de una publicación («5803757», el número de `codigo=` en su liga).
ordenamientoNoSólo lo que cambia este ordenamiento, por su clave: «LISR», «LIVA», «LIF», «CFF», «LFD», «RMF».

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, so the safety profile carries no burden here. The description adds genuinely new behavior: records still being cross-checked against the DOF are suppressed from results, and it discloses the result shape (title, date, DOF link, each provision with its type, effective date, and whether it takes effect later than the rest of the decree) plus the count and paging contract.

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?

Front-loaded with the core purpose, then access modes, then return shape, then paging — a sensible order. It is a dense single paragraph with some example redundancy (the date-string and ordenamiento examples duplicate schema values), but no sentence is filler.

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 six all-optional parameters and no output schema, the description does the heavy lifting well: it explains what each result contains and how to fetch the remainder via `pagina`. The one gap is that it never says what happens when no parameter is supplied, so default behavior for a zero-argument call has to be discovered by trying.

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%, so the schema already documents every parameter, including the fecha/hasta interaction and the ordenamiento key pattern. The description restates those modes with matching examples («LISR», «5803757», «reforma fiscal 2027») rather than adding syntax or precedence rules beyond the schema; useful confirmation, but not new semantics.

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 in the very first clause: what the DOF published and what each decree changed. It then enumerates the four access modes (codigo_dof, fecha/hasta, ordenamiento, consulta) so an agent can tell this is a retrieval/search tool rather than a reading tool, and explicitly hands off to siblings (leer_disposicion, que_cambio_en_la_norma) for the drill-down.

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

Usage Guidelines4/5

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

Gives clear context for when to reach for it — looking up a publication by DOF note code, by day or date range, by statute key, or by free words — and names the follow-up calls with the exact field to pass (version_id, referencia + fecha). It stops short of stating exclusions, e.g. when to prefer a sibling for norm-level or jurisprudence queries, so the agent must infer the boundary.

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