Skip to main content
Glama

Días inhábiles

dias_inhabiles
Read-onlyIdempotent

Retrieve non-working days for a year by Mexican authority (LFT, CNBV, SAT), including reasons, types, sources, and warnings when a list may be incomplete.

Instructions

Días inhábiles de un año según una autoridad: lft, cnbv o sat. No lista los sábados y domingos por serlo, pero sí un día publicado que cae en fin de semana. Cada día trae su motivo, su tipo (descanso, o vacaciones del SAT, que en los plazos de declaraciones y pagos cuentan como hábiles) y su fuente. Si la lista de un año puede estar incompleta, lo advierte; con lft advierte siempre que no incluye los festivos ni las suspensiones de labores del artículo 715. Consulta la API de MéxicoAPI (la pública, o la de MEXICOAPI_BASE) y, si no responde, usa los datos del paquete y lo advierte. Con MEXICOAPI_SIN_RED=1 responde con los datos del paquete, sin red.

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": {
      "autoridad": "<autoridad>",
      "anio": "<anio>"
    },
    "name": "dias_inhabiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
anioYesAño de 4 cifras.
autoridadYeslft: sábados, domingos y días de descanso obligatorio del artículo 74 de la Ley Federal del Trabajo, sin los festivos del calendario oficial ni los días en que las autoridades laborales suspenden labores (artículo 715); cnbv: calendario bancario, los días en que cierran las entidades financieras (no el de la CNBV como autoridad); sat: Código Fiscal de la Federación, artículo 12, por regla, y vacaciones del SAT.

Output Schema

NameRequiredDescriptionDefault
as_ofYesFecha de corte del dataset: la de la última actualización que lo cambió (en los datos curados, la publicación más reciente de sus fuentes). No es la fecha del valor, que va en datos.
datosYes
avisosYesLas advertencias con su código estable: avisos[i].texto es advertencias[i]. Un código desconocido vale como otro.
fuenteYesFuente para citar el dato.
origenYesapi: la API de MéxicoAPI; paquete: los datos y las reglas del paquete mexicoapi, sin red.
fuentesYesTodas las fuentes de la respuesta, empezando por fuente.
advertenciasYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly/openWorld/idempotent) by disclosing the data-acquisition behavior: it queries MéxicoAPI (public or MEXICOAPI_BASE), falls back to bundled package data with a warning if the API does not respond, and can be forced offline with MEXICOAPI_SIN_RED=1. It also discloses completeness caveats — warnings for possibly incomplete year lists and the always-on warning that lft excludes official holidays and article 715 work suspensions — and explains that SAT vacation days count as business days for filing deadlines.

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 is front-loaded in the first clause, then caveats and fallback behavior follow in a logical order. Sentences are long and densely chained with commas, which slightly reduces scannability, but nearly every clause carries actionable information rather than filler.

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?

Despite a simple two-parameter schema, the tool has real operational complexity (network dependency, fallback, environment override, per-authority caveats) and the description covers all of it. Since an output schema exists, it correctly avoids enumerating return fields while still explaining the per-day motivo/tipo/fuente semantics and the meaning of tipo for filing deadlines.

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%: the enum descriptions already define lft, cnbv and sat, including the article references and the note that cnbv means the banking calendar rather than the CNBV authority. The description only restates the authority list and the year, so it adds little meaning beyond the schema; baseline 3 is appropriate.

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+resource+scope: non-working days for a given year under a given authority (lft, cnbv, sat). It even delineates what the result is not (Saturdays and Sundays are not listed, but a published day falling on a weekend is), which lets an agent distinguish it from a date-arithmetic sibling like sumar_dias_habiles without reading 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 Guidelines3/5

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

Usage is implied rather than stated: it is a per-year holiday listing, so an agent can infer it should be used for holiday lookups and not for adding business days. There is no explicit when-to-use / when-not-to-use statement, no exclusion of alternatives, and no mention of the sibling tool that presumably computes day offsets.

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