Skip to main content
Glama
Sign In
cn-holiday-mcp

cn-holiday-mcp

by qianwei2333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_holidays

Retrieve official Chinese public holiday schedules for a specified year or all available years, including holiday periods, durations, and makeup workdays.

Instructions

列出某一年（或全部已收录年份）的法定节假日安排，包括放假区间、天数与调休上班日。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo年份，如 "2026"；缺省时返回全部已收录年份

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It clearly discloses that the tool returns holiday periods, day counts, and adjusted work days, and that omitting the year returns all recorded years. This goes beyond a simple 'list holidays' to specify the output content, though it does not mention side effects or read-only nature (implicit).

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?

The description is a single sentence that is concise and front-loaded. It starts with the action and resource, provides the scoping condition, and enumerates the output contents. 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?

The tool is simple with one optional parameter and no output schema. The description covers the main functionality and parameter behavior. It does not specify the exact return format (e.g., array structure), but given minimal complexity and the presence of content details, it is sufficiently complete.

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% for the 'year' parameter, so the schema already explains it. The description paraphrases the parameter (year or all years) without adding significant new meaning. It is adequate but does not enhance beyond the schema.

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 clearly states the tool lists statutory holiday arrangements for a given year or all recorded years, specifying included details (holiday periods, number of days, adjusted working days). This is a specific verb+resource that distinguishes it from a generic 'query' tool.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool vs the sibling tool 'query_holiday'. The description only implies its use for listing holidays, but does not mention alternatives or exclusions. It gives a default behavior hint (returns all years if year omitted), but no when-to-use or when-not-to-use comparison.

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

Deploy Server

Other Tools