Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

Holidays of a year

holidays
Read-onlyIdempotent

Holidays of a year: Jewish (hebrew; Israel or diaspora), Islamic, Chinese festivals, Christian (Easter and the movable feasts, Western and Orthodox), Persian (Nowruz), Indian national, Ethiopian (Enkutatash, Meskel) or Coptic (Nayrouz). "year" is a Gregorian year; "calendarYear" is the calendar's own year instead. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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": {
      "calendar": "<calendar>"
    },
    "name": "holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoGregorian year (default this year).
israelNoHebrew only: Israel's schedule.
methodNoIslamic method: umalqura (default, Saudi Arabia's official calendar), civil or tabular.
includeNoHebrew only: categories, comma-separated (major, minor, fast, modern, roshchodesh).
calendarYesWhich holidays.
traditionNoChristian only: western, orthodox or both.
calendarYearNoThe calendar's own year (not for christian).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context about what content is returned (which traditions and sub-traditions are included, that movable feasts come with Easter, that Israel's schedule differs from diaspora), though it says nothing about result shape or ordering.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The definition is front-loaded with the useful content, but the opening calendar enumeration is dense and the closing marketing line pointing to more FitzTopPicks APIs earns no place in a tool definition. The core guidance could be tightened without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter tool with no output schema, the description covers the input semantics reasonably but never indicates what is returned (holiday names, dates, both?) or the default behavior when optional parameters like tradition or include are omitted. An agent can call it correctly but cannot predict the response.

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 the baseline is 3, but the description adds real meaning beyond the schema: it explicitly frames 'year' as a Gregorian year and 'calendarYear' as the calendar's own year as a mutually exclusive alternative ('instead'). It stops short of explaining interactions such as how israel/include/method are ignored when calendar is not hebrew or islamic.

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 opens with a specific verb-and-resource statement ('Holidays of a year') and then enumerates the exact calendar families covered (Hebrew, Islamic, Chinese, Christian, Persian, Indian, Ethiopian, Coptic) with sub-variants such as Israel vs. diaspora and Western vs. Orthodox. This makes it clearly distinguishable from siblings like convert_date, calendar_months, or list_calendars.

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 only implied: the agent can infer it should call this when it needs holiday dates for a given calendar, but the description never states when to prefer it over alternatives (e.g., using list_calendars first to discover supported calendars) nor any failure conditions. The year-vs-calendarYear sentence is helpful guidance but is about parameter selection, not tool selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources