Skip to main content
Glama
Sign In

reference-data

by dev.asiaref
OverviewDiscussionsAdmin

get_public_holidays

Read-onlyIdempotent

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

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.

Output Schema

NameRequiredDescriptionDefault
unitNo
errorNoPresent on a free refusal or error; no charge
notesNo
staleNo
valueNo
seriesNo
sourceNo
countryNo
no_chargeNo
price_usdNo
confidenceNo
disclaimerNo
how_to_payNo
bind_seriesNo
explanationNo
label_basisNoInputs and the rule ids that produced the two labels
subdivisionNo
x_next_bindNo
http_endpointNo
coverage_labelNoHow much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules
effective_fromNo
last_confirmedNo
confidence_labelNoEvidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules
payment_requiredNotrue when the call needs payment; how_to_pay explains x402 or card
available_subdivisionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / label_basis / properties / source_type / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / label_basis / properties / source_type / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / label_basis / properties / verification_age_days / anyOf
      Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / label_basis / properties / verification_age_days / type
      Added value: +[
+  "number",
+  "null"
+]
  2. Changed3 schema fields changed
    • addedOutput schema / properties / confidence_label
      Added value: +{
+  "description": "Evidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules",
+  "enum": [
+    "high",
+    "medium",
+    "low"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / coverage_label
      Added value: +{
+  "description": "How much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules",
+  "enum": [
+    "ready",
+    "partial",
+    "gap"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / label_basis
      Added value: +{
+  "additionalProperties": {},
+  "description": "Inputs and the rule ids that produced the two labels",
+  "properties": {
+    "confidence_reasons": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "coverage_reasons": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "inputs": {
+      "items": {},
+      "type": "array"
+    },
+    "rules": {
+      "type": "string"
+    },
+    "rules_version": {
+      "type": "string"
+    },
+    "source_type": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "stale": {
+      "type": "boolean"
+    },
+    "verification_age_days": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "Holiday calendar series with cited source; with subdivision, merged national+regional days",
+  "properties": {
+    "available_subdivisions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "bind_series": {},
+    "confidence": {},
+    "country": {
+      "type": "string"
+    },
+    "disclaimer": {},
+    "effective_from": {},
+    "error": {
+      "description": "Present on a free refusal or error; no charge"
+    },
+    "explanation": {},
+    "how_to_pay": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "http_endpoint": {
+      "type": "string"
+    },
+    "last_confirmed": {},
+    "no_charge": {
+      "type": "boolean"
+    },
+    "notes": {},
+    "payment_required": {
+      "description": "true when the call needs payment; how_to_pay explains x402 or card",
+      "type": "boolean"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "series": {
+      "type": "string"
+    },
+    "source": {},
+    "stale": {
+      "type": "boolean"
+    },
+    "subdivision": {},
+    "unit": {},
+    "value": {},
+    "x_next_bind": {}
+  },
+  "type": "object"
+}
  4. 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"
+}
  5. 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"
+]
  6. 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"
+]
  7. 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"
+]
  8. 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"
+]
  9. 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"
+]
  10. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing cost ('FREE'), data provenance (official government source cited), and the merge/tagging behavior for regional calendars. No rate-limit or freshness details, so it stops short of a 5.

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?

Front-loaded with the cost signal and the core purpose, then a focused second sentence on sub-national behavior. Three clauses with little waste, though the subdivision sentence is dense and could be tightened.

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?

With an output schema present, the description need not explain return values, and it correctly focuses on scope, cost, provenance, and the subdivision flag. Complete enough for correct invocation, with the only real gap being routing guidance against the worldwide sibling.

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 baseline is 3. The description's explanation of `subdivision` (ISO 3166-2, 'DE-BY', merged with national statutory days, tagged national/regional) largely restates what the schema already documents, adding little beyond the structured field text.

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?

States a specific verb+resource ('official public-holiday calendar for a supported country') and adds scope details like gazetted movable holidays and government sourcing. It implicitly contrasts with the worldwide sibling via 'for a supported country', but never names get_public_holidays_worldwide, so the differentiation is left to inference.

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 clearly explains when to pass `subdivision` versus omitting it, which is genuine usage guidance. However, it gives no guidance on when to choose this tool over get_public_holidays_worldwide, get_calendar, or the business-day siblings, and no explicit exclusions.

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