calendar-mcp

Query Holiday

query_holiday

查询指定公历日期的中国法定节假日或调休安排，同时返回农历信息。支持2025、2026年。参数date格式：YYYY-MM-DD

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": {
      "date": "<date>"
    },
    "name": "query_holiday"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes	公历日期，格式 YYYY-MM-DD，如 "2026-10-01"

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 9, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / date / description

Added value: +"公历日期，格式 YYYY-MM-DD，如 \"2026-10-01\""

removedInput schema / properties / date / title
```
Removed value: -"Date"
```

removedInput schema / title

Removed value: -"query_holidayArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A3.5/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 and does contribute real behavior: it returns make-up workday (调休) arrangements as well as holidays, and it is limited to 2025 and 2026. It does not state what happens for out-of-range years or invalid dates (error vs empty result), which matters for a constrained lookup tool, so it is adequate but incomplete.

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 compact sentences: what it returns, supported years, then parameter format — front-loaded and scannable. The final format sentence duplicates the schema and could be dropped, keeping it just short of full marks.

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?

An output schema exists, so return-value detail is handled elsewhere, and the description supplies the crucial scope constraint (2025/2026) plus the make-up workday nuance. Only the out-of-range/invalid-date behavior is missing, which is a minor gap for a one-parameter lookup.

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% and the single date parameter already documents format 'YYYY-MM-DD' with an example, so the description's format sentence is largely redundant. Baseline 3 applies since the schema does the heavy lifting and no extra meaning (e.g., accepted range limits per year) is added.

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?

Description names a specific verb and resource: query Chinese statutory holiday or make-up workday (调休) status for a given Gregorian date, plus lunar info. The 2025/2026 scope and the dual return content make the purpose unambiguous, though it never explicitly distinguishes itself from the sibling solar_to_lunar, which plausibly returns similar lunar data.

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?

Usage is implied by the phrase '指定公历日期' (a specified Gregorian date), which suggests this is a single-date lookup rather than an enumeration. However, no guidance is given on when to prefer list_holidays (listing) or solar_to_lunar (conversion), and the overlap with solar_to_lunar on lunar output is left unexplained, so the agent must infer routing.

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

All calendar-mcp tools Inspect

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.