Skip to main content
Glama
Sign In

web2mcp

by io.github.charleswei118
OverviewDiscussionsAdmin

Public holidays: list

holidays_list
Read-only

[holidays] List the public holidays of one country for one year, e.g. to tell whether a date is a day off or plan around a holiday. Returns entries of date (YYYY-MM-DD), name (English) and localName (in the country's language). Weekends are not listed. Returns an error for a country Nager.Date does not cover; for mainland China make-up workdays (调休) use holidaycn_year instead.

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>",
      "country": "<country>"
    },
    "name": "holidays_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesFour-digit year, e.g. 2026
countryYesTwo-letter ISO 3166-1 country code in capitals, e.g. 'US', 'DE', 'TR'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds the parts annotations cannot — the returned fields (date as YYYY-MM-DD, name in English, localName in local language), the exclusion of weekends, and the error behavior for countries outside Nager.Date's coverage.

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?

One compact paragraph, front-loaded with the core action before the use case, then return shape, then boundary conditions. Every clause carries information an agent needs; nothing is redundant with the title or schema.

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?

With no output schema, the description supplies the return value shape itself; with only two fully documented parameters, no parameter prose is needed. Coverage limits, weekend exclusion and the China fallback round out everything required to call this correctly or route elsewhere.

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% and both parameters are fully documented in the schema (year range 1975-2075 with example, country as two-letter ISO code with examples), so the description adds no parameter meaning beyond that. Baseline 3 is appropriate when the schema carries the full burden.

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 states a specific verb and resource ('List the public holidays'), narrows the scope to 'one country for one year', and explicitly contrasts with the sibling holidaycn_year for mainland China make-up workdays. An agent can separate this from holidaycn_year 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 concrete motivating use case ('tell whether a date is a day off or plan around a holiday'), states the exclusion (weekends are not listed), names the failure condition (unsupported country returns an error), and names the exact alternative for the one case this tool does not serve. When-to-use, when-not-to-use and the alternative are all present.

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

All web2mcp toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources