Skip to main content
Glama
jalali-calendar-mcp

jalali-calendar-mcp

Is it a day off?

is_holiday
Read-onlyIdempotent

Check if a Gregorian (YYYY-MM-DD) or Jalali (YYYY/MM/DD) date is a Friday or official holiday in Iran and identify the holiday.

Instructions

Whether a day is a Friday or an official holiday in Iran, and which.

Args: value: Gregorian YYYY-MM-DD or Jalali YYYY/MM/DD.

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": {
      "value": "<value>"
    },
    "name": "is_holiday"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Output Schema

NameRequiredDescriptionDefault
jalaliYesThe day, Jalali YYYY/MM/DD.
holidaysYesOfficial holidays on this day, if any.
gregorianYesThe day, Gregorian (ISO 8601).
is_fridayYesFriday, the weekly day off.
is_day_offYesA Friday or an official holiday.
weekday_enYesEnglish weekday.
weekday_faYesPersian weekday.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and a closed-world read, so safety needs no restating. The description adds real domain context beyond them: that Friday counts as a day off in the Iranian week and that the result also identifies which holiday applies. It stops short of saying what happens for malformed dates or out-of-range calendars.

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?

The core behavior is front-loaded in one sentence and the argument note is compact with no filler. The phrase 'and which' is slightly loose, leaving the agent to infer that the holiday name is returned.

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 predicate with an output schema and read-only annotations, the definition covers the essentials: what is checked, the Iranian Friday rule, and the accepted date formats. Remaining gaps (invalid-input behavior) are minor given the output schema carries the return shape.

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%, so the description must carry the parameter, and it does: it documents both accepted calendar formats with concrete layouts (Gregorian YYYY-MM-DD vs Jalali YYYY/MM/DD). It does not address invalid input or ambiguity between the two formats, which keeps it below a 5.

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?

The description states a specific check ('Whether a day is a Friday or an official holiday in Iran, and which'), which tells an agent exactly what comes back: a boolean plus holiday identity. It does not distinguish itself from siblings like get_holidays or count_workdays, so an agent must infer that this is the single-date lookup.

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 by the purpose: check one specific date rather than list holidays or count workdays. There is no explicit when-to-use/when-not guidance and no named alternative for bulk or range queries.

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