calendar-mcp

List Holidays

list_holidays

列出指定年份的全部中国法定节假日安排，包括放假日期和调休上班日期。支持2025、2026年

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": {
      "year": "<year>"
    },
    "name": "list_holidays"
  }
}

Input Schema

Name	Required	Description	Default
`year`	Yes	年份，如 2026

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 / year / description
```
Added value: +"年份，如 2026"
```
- removedInput schema / properties / year / title
```
Removed value: -"Year"
```
- removedInput schema / title
```
Removed value: -"list_holidaysArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedSep 6, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose that both holiday dates and make-up working days (调休) are included, which is substantive content information, but it says nothing about ordering, volume, or whether the year must fall in the supported range (behavior for 2024/2027 is undefined).

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, no filler: the first states the operation and what is returned, the second states the supported-year limit. Front-loaded and every clause earns its place.

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 not required, and the single parameter is fully described. The only shortfall is the absent routing guidance relative to query_holiday, which matters for a tool set with overlapping holiday functionality.

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% and only one parameter exists, so the baseline is already satisfied. The description goes beyond the schema by stating the accepted year range (2025, 2026), a constraint the integer schema does not encode with an enum or bounds.

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+scope: '列出指定年份的全部中国法定节假日安排' plus the two categories of content returned (放假日期 and 调休上班日期). The word '全部' implicitly separates it from query_holiday, but no sibling is named, so 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 supported-year clause ('支持2025、2026年') gives a usage constraint, but there is no explicit guidance on when to pick this tool over query_holiday or solar_to_lunar. The agent must infer that 'all holidays for a year' vs 'query a specific holiday' is the dividing line.

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.