Skip to main content
Glama

Festivos de Colombia

co-holidays
Read-onlyIdempotent

Lista los 18 (hasta 2025) o 19 (desde 2026, Ley 2578 de 2026) festivos nacionales de Colombia de un año según la Ley Emiliani (traslado a lunes) y la Pascua. Cuándo: hay que aplicar con exactitud una regla colombiana (DIAN, festivos de la Ley Emiliani, montos en COP, IVA, GMF, UVT), p. ej. al facturar o cobrar. No para: indicar si una fecha es festivo nacional en Colombia (co-is-holiday). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Lists the 18 (until 2025) or 19 (from 2026, Ley 2578 de 2026) Colombian national holidays for a year, applying Ley 51 de 1983 (Ley Emiliani) Monday moves and Easter dates (Holy Week, Ascension, Corpus Christi, Sacred Heart). When: a Colombian rule (DIAN, Ley Emiliani holidays, COP amounts, IVA, GMF, UVT) has to be applied exactly, e.g. in invoicing or payment flows. [EN completo / full EN: inputSchema.description]

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": {
      "year": "<year>"
    },
    "name": "co-holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesYear (1984 onward, when Ley 51 de 1983 took effect) (integer; required; min 1984; max 2200).

Output Schema

NameRequiredDescriptionDefault
yearNo
countNo
holidaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"EN: Lists the 18 Colombian national holidays for a year, applying Ley 51 de 1983 (Ley Emiliani) Monday moves and Easter-based dates (Holy Week, Ascension, Corpus Christi, Sacred Heart). When: a Colombian rule (DIAN, Ley Emiliani holidays, COP amounts, IVA, GMF, UVT) has to be applied exactly, e.g. in invoicing or payment flows. Not for: saying whether a date is a Colombian national holiday (co-is-holiday). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."New value: +"EN: Lists the 18 (until 2025) or 19 (from 2026, Ley 2578 de 2026) Colombian national holidays for a year, applying Ley 51 de 1983 (Ley Emiliani) Monday moves and Easter dates (Holy Week, Ascension, Corpus Christi, Sacred Heart). When: a Colombian rule (DIAN, Ley Emiliani holidays, COP amounts, IVA, GMF, UVT) has to be applied exactly, e.g. in invoicing or payment flows. Not for: saying whether a date is a Colombian national holiday (co-is-holiday). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."
  2. Changed1 schema field changed
    • addedInput schema / properties / year / examples
      Added value: +[
      +  2026
      +]
  3. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Lists the 18 Colombian national holidays for a year, applying Ley 51 de 1983 (Ley Emiliani) Monday moves and Easter-based dates (Holy Week, Ascension, Corpus Christi, Sacred Heart). When: a Colombian rule (DIAN, Ley Emiliani holidays, COP amounts, IVA, GMF, UVT) has to be applied exactly, e.g. in invoicing or payment flows. Not for: saying whether a date is a Colombian national holiday (co-is-holiday). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."
  4. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint=false, idempotentHint and destructiveHint=false, and the description largely restates them ('solo lectura, sin red, sin estado guardado', 'determinista'). What it does add beyond the annotations are operational limits (64 KB input, 1 s per call, 1 MB result), which is genuine if modest extra context; nothing is said about ordering or result shape, though an output schema covers returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and exclusion are front-loaded, which is good, but the text is padded by a full Spanish/English duplication that culminates in a cross-reference ('[EN completo / full EN: inputSchema.description]') pointing to text the agent already has. The generic Colombian-rules enumeration in the 'Cuándo' clause is boilerplate that does not earn its space for a holiday tool.

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?

For a one-parameter read-only tool with full annotations and an output schema, the definition covers scope, legal basis, sibling exclusion, side effects and resource limits — essentially everything needed to call it correctly. The only shortfall is the awkward pointer to the input schema for the full English text instead of stating it directly (or omitting the duplicate).

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% with the single 'year' parameter fully documented (min 1984, max 2200, example, and the 1984 legal rationale). The description adds only the year-dependent holiday count (18 vs 19), which gives contextual meaning to why the year matters but not format or validation details beyond the schema; baseline 3 applies.

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 (lists Colombian national holidays for a year), quantifies the scope (18 until 2025, 19 from 2026 under Ley 2578), and names the legal basis (Ley 51 de 1983 / Ley Emiliani, Easter-derived dates). It explicitly distinguishes itself from the sibling co-is-holiday, so an agent can route between the two without opening either 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?

The 'No para' clause is a clean exclusion that names the alternative (co-is-holiday) for single-date checks, which is exactly the disambiguation an agent needs. The positive 'Cuándo' clause, however, is generic boilerplate covering all Colombian rules (DIAN, COP, IVA, GMF, UVT) rather than the specific condition that selects this holiday-listing tool, which dilutes the guidance.

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