TimeTree MCP Server

get_holidays

Read-only

Look up public holidays and observances for up to 5 countries within a 2-year date range, sorted by date. Check day_off status to identify non-working days.

Instructions

Look up public holidays and observances for up to 5 countries in a date range of up to 2 years, sorted by date. day_off tells whether it is a day off. These are national holidays, not events in your calendars (use get_events for those).

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_iso": "<country_iso>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_holidays"
  }
}

Input Schema

Name	Required	Description
`end_date`	Yes	Last date to include (YYYY-MM-DD, UTC)
`start_date`	Yes	First date to include (YYYY-MM-DD, UTC)
`country_iso`	Yes	ISO 3166-1 alpha-2 country codes, e.g. ["KR"] or ["KR", "JP"] (max 5)
`days_off_only`	No	Only return days off, excluding observances that are working days (default: false)

Output Schema

Name	Required	Description	Default
`total`	Yes
`holidays`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.0Oct 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "holidays": {
+      "items": {
+        "properties": {
+          "country_iso": {
+            "type": "string"
+          },
+          "date": {
+            "description": "YYYY-MM-DD",
+            "type": "string"
+          },
+          "day_off": {
+            "type": "boolean"
+          },
+          "end_date": {
+            "description": "YYYY-MM-DD",
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "date",
+          "title",
+          "day_off"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "holidays",
+    "total"
+  ],
+  "type": "object"
+}

Addedv0.4.0Oct 3, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: the 5-country cap, the 2-year range cap, the date sort order, and what day_off means in the response. It does not mention rate limits or behavior when a country has no data, so it falls 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.

Conciseness5/5

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

Three short sentences, all front-loaded: capability and limits first, the day_off note second, sibling disambiguation last. Every sentence carries non-redundant information.

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?

An output schema exists, so return values need not be explained, yet the description still clarifies the key output field (day_off). Combined with annotations and full schema coverage, an agent has everything needed to call and interpret it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds the 2-year date-range constraint that does not appear in the schema and clarifies the intent of days_off_only via the day_off concept. It does not add format or edge-case detail for country_iso beyond what the schema already documents.

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 verb (look up) and resource (public holidays and observances), plus hard scope limits: up to 5 countries, up to a 2-year range, sorted by date. It explicitly separates itself from calendar events by naming get_events, so an agent can distinguish it from siblings without opening either schema.

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

Usage Guidelines5/5

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

It gives a direct when-to-use rule (national holidays) and a when-not rule with a named alternative: 'not events in your calendars (use get_events for those)'. The only thing missing is whether days_off_only filtering is preferred in certain cases, which is minor.

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