Skip to main content
Glama

Biblioteca abierta de Cumplida

Leer completa una disposición

leer_disposicion
Read-onlyIdempotent

Lee completa la versión aprobada de una disposición fiscal mexicana que regía el día del hecho, por su referencia («LISR 28», «art. 27 LISR», «regla 3.13.4») o el version_id de normativa_vigente, con su vigencia, el decreto del DOF que le dio ese texto y la compilación de donde se tomó, si fue de una. fecha (AAAA-MM-DD) o periodo (AAAA-MM) eligen la versión; sin ellas, la de hoy. Léala antes de afirmar algo de ella; si la respuesta trae sigue_desde, llame otra vez con desde igual a ese número.

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": "leer_disposicion"
  }
}

Input Schema

NameRequiredDescriptionDefault
desdeNoDesde qué carácter seguir el texto, cuando la respuesta anterior dijo `sigue_desde`.
fechaNoEl día del hecho (AAAA-MM-DD): elige la versión que regía ese día. Sin ella, la de hoy.
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).
referenciaNoLa disposición: «CFF 69-B», «art. 27 LISR», «regla 2.7.1.21». O `version_id`.
version_idNoEl `version_id` que dio otra herramienta: lee esa versión exacta.

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. Changed3 schema fields changed
    • addedInput schema / properties / fecha / description
      Added value: +"El día del hecho (AAAA-MM-DD): elige la versión que regía ese día. Sin ella, la de hoy."
    • addedInput schema / properties / referencia / description
      Added value: +"La disposición: «CFF 69-B», «art. 27 LISR», «regla 2.7.1.21». O `version_id`."
    • addedInput schema / properties / version_id / description
      Added value: +"El `version_id` que dio otra herramienta: lee esa versión exacta."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld=false and non-destructive, so the safety profile is covered. The description still adds real value beyond them by disclosing the payload (vigencia, the DOF decree that gave the text, the compilation it came from) and the `sigue_desde`/`desde` pagination contract, plus the default-to-today rule. Missing only failure behavior when a reference resolves to nothing.

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 action and resource, then the reference forms, then the version-selection rule, then the read-before-asserting directive. Every sentence carries information, though the single dense paragraph is somewhat run-on and would scan better split into a purpose line plus behavior lines.

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?

Five optional parameters, no output schema, no enums — the description compensates by explaining what the response contains, how the version is chosen by default, and how to continue reading across chunks. An agent has everything needed to call it correctly and to interpret the result, including its relationship to `normativa_vigente`.

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%, so every parameter — including the pattern-constrained `fecha`/`periodo` and the `desde` offset — is already documented in the schema. The description mostly restates the schema's own semantics (reference examples, date-vs-period selection, today as default) and only adds the pagination loop as genuinely new meaning. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb and resource: reads the complete approved version of a Mexican tax provision in force on the date of the event, and lists accepted reference forms («LISR 28», «art. 27 LISR», «regla 3.13.4») plus `version_id`. It also differentiates from siblings by identifying `normativa_vigente` as the source of `version_id`, so an agent can distinguish it from precedent/jurisprudence tools without opening any schema.

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 an explicit operational directive — read the provision before asserting anything about it — and describes the default when `fecha`/`periodo` are omitted (today's version). It also explains the pagination follow-up when `sigue_desde` appears in the response. It stops short of explicit when-not guidance (e.g., deferring index/lookup questions to `normativa_vigente`).

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