Skip to main content
Glama

Public holidays

holidays

Public holidays for a country and year from date.nager.at. Cached for 24 hours. Returns date, name, and local name.

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_code": "<country_code>"
    },
    "name": "holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoCalendar year. Defaults to the current UTC year.
country_codeYesISO country code, for example US, or a common country name.

Output Schema

NameRequiredDescriptionDefault
okNo
yearNo
countryNo
holidaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations present the description carries the full burden, and it does disclose the upstream provider, a 24-hour cache (useful freshness signal), and the returned fields. It stops short of covering failure modes such as an unrecognized country code or upstream outages.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the resource and scope, then the caching trait, then the payload. Nothing is redundant and nothing important is buried.

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?

The tool is simple (one required, one optional parameter), the schema is fully described, and an output schema exists so return values need no elaboration. The only meaningful omission is behavior on invalid input or upstream failure, which would round out an otherwise complete definition.

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 description coverage is 100%, so both parameters are already documented, including the year default and ISO country code examples. The description only restates that a country and year are needed, adding no new meaning beyond the schema.

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 resource (public holidays), its scope (a country and a year), and its data source (date.nager.at). An agent can immediately tell this apart from temporal siblings such as date_math, time, and time_convert.

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?

The scope constraint (country + year) implies when the tool applies, but there is no explicit when-to-use or when-not-to-use guidance and no alternative is named. The agent must infer that this is the tool for holiday lookups rather than date computation.

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