Skip to main content
Glama
jalali-calendar-mcp

jalali-calendar-mcp

Official holidays of a year

get_holidays
Read-onlyIdempotent

Retrieve Iran's official holidays for a specified Jalali year in chronological order. Use it to plan around public holidays; Fridays are excluded.

Instructions

Iran's official holidays in a Jalali year, in date order. Fridays are not listed.

Args: year: Jalali year, e.g. 1405.

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": "get_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes

Output Schema

NameRequiredDescriptionDefault
yearYes
holidaysYes
lunar_statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and a closed-world scope, so the safety profile needs no restating. The description adds genuinely useful behavior: results are date-ordered and Fridays are omitted, which prevents a wrong assumption about the list being exhaustive. It stops short of saying why Fridays are excluded or how the list interacts with weekend rules.

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?

Front-loaded one-line summary followed by an Args block; nothing is padded. The Args line partially restates the schema but earns its place by adding 'Jalali' and the example value.

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?

For a one-parameter read-only tool with an output schema, the description covers scope, ordering and the Friday exclusion, which is enough to call it correctly. Return value details are rightly left to the output schema, so remaining gaps are minor.

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 0% – the schema only says 'Year: integer' – so the description must carry the meaning, and it does: the year is Jalali (not Gregorian) and an example (1405) anchors the expected range. That is the single most important disambiguation for this parameter and it is supplied.

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 the specific resource (Iran's official holidays), the scoping unit (a Jalali year), the ordering (date order), and an exclusion (Fridays are not listed). An agent can tell this returns a list for a whole year, distinct from a single-day check like is_holiday, though it never names a sibling to contrast with.

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 resource description – fetch the full holiday list for a year – but there is no explicit when-to-use versus when-not-to-use guidance. Nothing tells the agent to prefer is_holiday for a single date or count_workdays for working-day math, so the routing must be inferred.

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