Skip to main content
Glama

Próximos festivos de un país (93 países)

holiday-world-next
Read-onlyIdempotent

Lista los próximos festivos nacionales de uno de 93 países desde una fecha dada (2024-2030), con los días que faltan para cada uno, según festivos calculados con date-holidays; la fecha se da explícitamente (sin reloj), así que el resultado es determinista. Cuándo: se necesitan los próximos festivos nacionales de un país a partir de una fecha dada. No para: listar los festivos nacionales de un país y año (holiday-world-list). 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 next national public holidays of one of 93 countries on or after a given date (2024-2030), with the days until each, from holidays computed at build time with date-holidays; the date must be given explicitly (no clock), so the result is deterministic. [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": {
      "n": 3,
      "from": "2026-11-03",
      "country": "BR"
    },
    "name": "holiday-world-next"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNoHow many holidays (integer; optional; default 5; min 1; max 20).
fromYesStart date, inclusive (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
fromNo
noteNo
countNo
sourceNo
countryNo
holidaysNo
truncatedNo
matched_byNo
name_languageNo
country_name_enNo
country_name_esNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, and the description reinforces this with 'sin red, sin estado guardado' plus concrete limits (64 KB input, 1 s per call, 1 MB result) and the determinism caveat that the date must be supplied explicitly. The only gap is behavior outside the stated 2024-2030 window or with an unrecognized country code, which is not described.

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?

The Spanish paragraph is front-loaded and dense: purpose, then when, then not-for, then side effects, determinism and limits each in one clause. The trailing '[EN completo / full EN: ...]' duplication of the same content already repeated in inputSchema.description is redundant, which keeps it from a 5.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. What remains for a 3-param read-only lookup tool — scope, coverage years, determinism, limits and the competing sibling — is all present.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents n, from and country in detail; the description adds value with the 2024-2030 validity window and the 'no clock, date given explicitly' constraint on `from`, plus the fact that output includes days-until per holiday. It does not add anything about the `n` cap or accepted country-code formats beyond what the schema states, so it stays at 4 rather than 5.

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: lists the *next* national public holidays for one of 93 countries on or after a given date, within 2024-2030, including days-until. It explicitly names the sibling holiday-world-list as the different tool, so an agent can distinguish them 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 an explicit 'Cuándo:' trigger condition (next national holidays of a country after a given date) and an explicit 'No para:' exclusion routing year-based listing to holiday-world-list. Both when-to-use and when-not-to-use are present with the alternative named.

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