Skip to main content
Glama

List public holidays for a country and year

holidays
Read-only

Public holidays of a country (ISO 2 code) for a year (default: this year): date, local and English names, and whether the holiday is nationwide or regional with its counties. Source: Nager.Date. An empty list is a valid answer. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
yearNo1900 to 2100 (default: this year)
countryYesISO 3166 alpha-2 code, e.g. DE

Output Schema

NameRequiredDescriptionDefault
yearNo
countNo
sourceNo
countryNo
holidaysNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations already mark it read-only and open-world, but the description adds non-obvious behavior: x402 payment cost, no charge on failure, Nager.Date source, and that an empty list is a valid result.

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 description front-loads purpose and return fields, then adds source, empty-result semantics, and pricing. Each sentence carries distinct value, though the pricing parenthetical is slightly dense.

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?

Given low complexity, full schema coverage, an output schema, and annotations, the description covers remaining agent-relevant context such as payment, source, and empty-result handling.

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%, so both parameters are fully documented in the schema. The description restates country ISO 2 and the year default but adds no syntax or format detail beyond the schema.

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?

The description names the resource (public holidays), the scope (country ISO code and year), and the returned fields, so an agent can identify the operation. It does not explicitly differentiate from siblings such as business_days.

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?

No explicit when-to-use or when-not-to-use guidance is given, and no alternative tool is named. The operation is largely self-explanatory, so usage is only implied.

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