Skip to main content
Glama

Festivos nacionales de un año (93 países)

holiday-world-list
Read-onlyIdempotent

Lista los festivos nacionales de uno de 93 países para un año entre 2024 y 2030, con fechas, nombre local e inglés y marca de día sustituto, según festivos calculados con date-holidays; no cubre festivos regionales. Cuándo: se necesitan los festivos nacionales de un país y año para planear o calcular plazos. No para: listar los 18 (hasta 2025) o 19 (desde 2026) festivos nacionales de Colombia de un año (co-holidays). 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 national public holidays of one of 93 countries for a year between 2024 and 2030, with dates, local and English names and substitute-day flags, from holidays computed at build time with date-holidays; regional holidays are not covered. When: the national public holidays of a country and year are needed for planning or deadlines. [EN completo / full EN: inputSchema.description]

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": 2026,
      "country": "ES"
    },
    "name": "holiday-world-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesYear (integer; required; min 2000; max 2100).
countryYesCountry: ISO 3166-1 alpha-2 (CO) or alpha-3 (COL) code, or name in English or Spanish (Colombia, Alemania, Germany) (string; required; at least 1 chars; up to 80 chars).

Output Schema

NameRequiredDescriptionDefault
noteNo
yearNo
countNo
sourceNo
countryNo
holidaysNo
matched_byNo
name_languageNo
country_name_enNo
country_name_esNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"EN: Lists the national public holidays of one of 93 countries for a year between 2024 and 2030, with dates, local and English names and substitute-day flags, from holidays computed at build time with date-holidays; regional holidays are not covered. When: the national public holidays of a country and year are needed for planning or deadlines. Not for: listing the 18 Colombian national holidays for a year, applying Ley 51 de 1983 (co-holidays). 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 national public holidays of one of 93 countries for a year between 2024 and 2030, with dates, local and English names and substitute-day flags, from holidays computed at build time with date-holidays; regional holidays are not covered. When: the national public holidays of a country and year are needed for planning or deadlines. Not for: listing the 18 (until 2025) or 19 (from 2026) Colombian national holidays for a year (co-holidays). 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. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-open-world, non-destructive; the description adds value beyond them by stating the holidays are precomputed at build time, that regional holidays are absent, that there are no side effects, no network and no stored state, plus concurrency limits (64 KB input, 1 s per call, 1 MB result). That is precisely the extra behavioral context annotations cannot express.

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 verb+scope, then cleanly labeled sections (Cuándo / No para / Efectos secundarios / Determinista / Límites), which is easy to scan. It is however substantially longer than needed because the entire content is duplicated in an English block, and the English block is cut off mid-reference to inputSchema.description.

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?

An output schema exists, so return values need not be explained, and the description still covers data source, coverage gaps, determinism, side effects and limits — sufficient for a 2-parameter read-only lookup. The only completeness defect is the year-range mismatch (2024-2030 in prose vs 2000-2100 in the schema), which could lead an agent to reject a valid input or trust a wrong bound.

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% and both parameters carry their own descriptions, so the baseline is 3. The description does add a constraint not in the schema (year must be 2024-2030), but that constraint conflicts with the schema's stated 2000-2100 range, which makes the added meaning unreliable rather than clarifying.

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 ("Lista los festivos nacionales"), the scope (93 countries, year range 2024-2030), and the exact fields returned (dates, local/English names, substitute-day flag). It also bounds the scope by excluding regional holidays and names the data source (date-holidays), so the agent can distinguish it from related calendar tools without opening the schema.

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

Usage Guidelines5/5

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

Has explicit "Cuándo" guidance (planning or deadline calculation for a country/year) and an explicit "No para" exclusion that routes Colombia-specific queries to the co-holidays sibling, including the count difference (18 until 2025, 19 from 2026). Both the positive and negative conditions are stated, leaving nothing to inference.

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