Skip to main content
Glama

holidays

Fetch official public holiday dates for a country and year, and check whether a specific date is one.

Instructions

Official public holidays for a country and year (100+ countries, Nager.Date open data), plus whether a given date is a holiday. Costs 0.001 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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
dateNooptional YYYY-MM-DD to test
yearNo4-digit year
countryYesISO 3166-1 alpha-2 country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the pricing model (0.001 USDC on Base per successful call via x402) and the specific failure mode (402 challenge without a payment key), plus the data provenance. It does not describe the response shape, since no output schema exists, nor how invalid country codes or years are handled.

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?

Three short sentences, front-loaded with the core capability and followed by cost and the payment-key caveat. Every sentence carries information; the payment detail is slightly dense but is necessary for correct invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations and no output schema, the description covers cost, payment failure behavior, and data source, which are the highest-risk unknowns. It still leaves the return payload undocumented and does not explain how the optional date relates to the year parameter when both are supplied.

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 the baseline is 3 — the schema already documents 'country' as ISO 3166-1 alpha-2, 'year' as 4-digit, and 'date' as YYYY-MM-DD. The description adds only the framing that date is used to test whether a given day is a holiday, and that country coverage spans 100+ codes; it adds no interaction rules between year and date.

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?

The description names a specific resource and scope: official public holidays for a country and year, drawing on Nager.Date open data across 100+ countries, plus a date-membership check. An agent can immediately tell what it returns without opening the schema, and no sibling in the catalog overlaps with holiday data.

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

Usage Guidelines4/5

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

It conveys the practical precondition for use — a payment key is required, otherwise the call returns a 402 challenge — which is the main gating condition an agent needs before invoking. There are no competing tools to route against, so the absence of explicit alternatives costs little; what is missing is guidance on when the optional date argument should be supplied versus a plain year lookup.

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