Skip to main content
Glama
API Colombia

API Colombia

by TernApp

Festivos de Colombia

festivos
Read-onlyIdempotent

Retrieve official Colombian public holidays for any year from 1984 to 2100, including original dates and whether each holiday was moved to Monday.

Instructions

Lista los festivos oficiales de Colombia de un año (1984–2100), con la fecha original y si se trasladaron al lunes. Desde 2026 son 19, por la Ley 2578 de 2026 (Virgen de Chiquinquirá).

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

Input Schema

NameRequiredDescriptionDefault
anioNoAño (por defecto, el año actual en Colombia)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered. The description still adds genuine context beyond that: the returned fields (original date and whether the holiday was moved to Monday) and the fact that from 2026 the count becomes 19 under Ley 2578 — domain facts an agent could not derive from structured fields.

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

Conciseness5/5

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

Two tight sentences with zero filler: the operation and scope come first, then the return content, then the legislative nuance. Every clause carries information an agent can act on.

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-optional-parameter read tool with no output schema, the description covers scope, return shape (dates plus Monday-relocation flag) and a notable rule change. Only the exact response structure and ordering are left unstated, which is minor at this complexity.

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% and the single parameter already documents its type, default (current year in Colombia) and min/max bounds. The description's year range merely restates the schema bounds, adding no new semantics such as format or timezone handling, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Lista los festivos oficiales de Colombia de un año" states a specific verb (list) and resource (official holidays) plus the valid year window, which implicitly separates it from a single-date check like es_festivo. It stops short of naming any sibling explicitly, so the differentiation must be inferred from the word "año".

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?

The description implies the use case (retrieve a full year's holiday calendar) but never says when to prefer it over es_festivo, calendario_dian or contar_dias_habiles. There are no explicit exclusions or prerequisite notes; an agent must infer routing from the year-scoped phrasing.

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