Skip to main content
Glama

¿Es festivo en este país? (93 países)

holiday-world-check
Read-onlyIdempotent

Indica si una fecha es festivo nacional en uno de 93 países (América, la mayor parte de Europa y países principales de África, Asia y Oceanía) para 2024-2030, con nombre local e inglés, según festivos calculados con date-holidays; no cubre festivos regionales. Cuándo: hay que saber si una fecha es festivo nacional en un país distinto de Colombia (o en Colombia desde una segunda fuente). 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: Tells whether a date is a national public holiday in one of 93 countries (the Americas, most of Europe and major countries of Africa, Asia and Oceania) for 2024-2030, with the local and English names, from holidays computed at build time with date-holidays; regional holidays are not covered. [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": {
      "date": "2026-11-16",
      "country": "MX"
    },
    "name": "holiday-world-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate to check (YYYY-MM-DD) (string; required; at least 10 chars; up to 10 chars).
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
dateNo
noteNo
sourceNo
countryNo
holidaysNo
is_holidayNo
matched_byNo
weekday_enNo
weekday_esNo
name_languageNo
country_name_enNo
country_name_esNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive, but the description adds material context: no network access, no stored state, deterministic output for the same input, holidays computed at build time, and hard limits (64 KB input, 1 s per call, 1 MB result). These operational characteristics are not available from the annotations or schema and materially affect how an agent should call it.

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 purpose and organized into labeled sections (Cuándo, No para, Efectos secundarios, Determinista, Límites), so each sentence earns its place. The main cost is that the Spanish text is followed by a near-complete English restatement and a pointer to inputSchema.description, which duplicates content already present elsewhere.

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?

For a two-parameter lookup tool this is fully specified: coverage, year range, data source and staleness, exclusions, safety profile, determinism, and per-call limits are all present, and an output schema exists so return values need no explanation. Nothing required to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters are documented in the schema (YYYY-MM-DD date; country as ISO alpha-2/alpha-3 or English/Spanish name) with examples and min/max lengths. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies — the schema, not the prose, carries the parameter burden.

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 (indicates whether a date is a national public holiday), plus scope: 93 countries enumerated by region, years 2024-2030, local and English names, computed with date-holidays, regional holidays excluded. It explicitly contrasts itself with the sibling co-is-holiday, so an agent can distinguish 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 Guidelines5/5

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

Provides explicit 'Cuándo' (when a non-Colombian country is involved, or Colombia from a second source) and 'No para' clauses that name the alternative tool co-is-holiday for the Colombian case. This is a textbook when-to-use / when-not-to-use / alternative routing statement, and the coverage limits (93 countries, 2024-2030, no regional holidays) further constrain selection.

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