Skip to main content
Glama

reference-data

by dev.asiaref
OverviewDiscussionsAdmin

get_public_holidays

FREE. Official public-holiday calendar for a supported country, including gazetted movable holidays, with the official government source cited. Some countries also carry sub-national calendars (e.g. the German Laender): the subdivisions field lists them, and passing subdivision (ISO 3166-2, e.g. 'DE-BY') returns the national calendar merged with that region's statutory days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYesISO country code
subdivisionNoOptional ISO 3166-2 region code (e.g. 'DE-BY'). Returns national + that region's statutory holidays, each tagged national/regional. Omit for the national calendar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / subdivision
      Added value: +{
+  "description": "Optional ISO 3166-2 region code (e.g. 'DE-BY'). Returns national + that region's statutory holidays, each tagged national/regional. Omit for the national calendar.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "ae",
-  "bd",
-  "bh",
-  "cn",
-  "hk",
-  "id",
-  "il",
-  "in",
-  "jp",
-  "kr",
-  "kw",
-  "kz",
-  "lk",
-  "my",
-  "om",
-  "ph",
-  "pk",
-  "qa",
-  "sa",
-  "sg",
-  "th",
-  "tr",
-  "tw",
-  "vn"
-]New value: +[
+  "ae",
+  "bd",
+  "bh",
+  "cn",
+  "hk",
+  "id",
+  "il",
+  "in",
+  "iq",
+  "jo",
+  "jp",
+  "kr",
+  "kw",
+  "kz",
+  "lk",
+  "my",
+  "np",
+  "om",
+  "ph",
+  "pk",
+  "qa",
+  "sa",
+  "sg",
+  "th",
+  "tr",
+  "tw",
+  "uz",
+  "vn"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "ae",
-  "bd",
-  "bh",
-  "cn",
-  "hk",
-  "id",
-  "il",
-  "in",
-  "jp",
-  "kr",
-  "kw",
-  "my",
-  "om",
-  "ph",
-  "pk",
-  "qa",
-  "sa",
-  "sg",
-  "th",
-  "tr",
-  "tw",
-  "vn"
-]New value: +[
+  "ae",
+  "bd",
+  "bh",
+  "cn",
+  "hk",
+  "id",
+  "il",
+  "in",
+  "jp",
+  "kr",
+  "kw",
+  "kz",
+  "lk",
+  "my",
+  "om",
+  "ph",
+  "pk",
+  "qa",
+  "sa",
+  "sg",
+  "th",
+  "tr",
+  "tw",
+  "vn"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "ae",
-  "bd",
-  "cn",
-  "hk",
-  "id",
-  "in",
-  "jp",
-  "kr",
-  "my",
-  "ph",
-  "pk",
-  "qa",
-  "sa",
-  "sg",
-  "th",
-  "tr",
-  "tw",
-  "vn"
-]New value: +[
+  "ae",
+  "bd",
+  "bh",
+  "cn",
+  "hk",
+  "id",
+  "il",
+  "in",
+  "jp",
+  "kr",
+  "kw",
+  "my",
+  "om",
+  "ph",
+  "pk",
+  "qa",
+  "sa",
+  "sg",
+  "th",
+  "tr",
+  "tw",
+  "vn"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "bd",
-  "id",
-  "in",
-  "jp",
-  "kr",
-  "my",
-  "ph",
-  "sg",
-  "th",
-  "vn"
-]New value: +[
+  "ae",
+  "bd",
+  "cn",
+  "hk",
+  "id",
+  "in",
+  "jp",
+  "kr",
+  "my",
+  "ph",
+  "pk",
+  "qa",
+  "sa",
+  "sg",
+  "th",
+  "tr",
+  "tw",
+  "vn"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "in",
-  "jp",
-  "kr",
-  "ph",
-  "sg"
-]New value: +[
+  "bd",
+  "id",
+  "in",
+  "jp",
+  "kr",
+  "my",
+  "ph",
+  "sg",
+  "th",
+  "vn"
+]
  7. First observed

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses 'FREE' and explains subdivision behavior, but lacks details on rate limits, error handling, or data freshness.

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?

Two sentences, front-loaded with key purpose and free status. Every sentence adds value; no wasted words.

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?

Covers main functionality and subdivision parameter well, but lacks description of response format (fields like date, name, type). With no output schema, this information would aid an AI agent.

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?

The description adds significant value beyond the schema: explains ISO 3166-2 format for subdivision, describes behavior for national vs merged calendars, and mentions the subdivisions field. This is crucial for correct parameter usage.

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 explicitly states 'Official public-holiday calendar for a supported country', including gazetted movable holidays and government source. This clearly distinguishes it from sibling tools like count_working_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?

The description does not explicitly state when to use vs alternatives, but implies usage for retrieving public holidays. No exclusions or comparative guidance are given.

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

All reference-data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources