Skip to main content
Glama
jalali-calendar-mcp

jalali-calendar-mcp

A Jalali month

get_month
Read-onlyIdempotent

Get every day of a Jalali month with its Gregorian date, weekday, Fridays and holidays. Provide a year and month number to retrieve the full monthly calendar.

Instructions

Every day of a Jalali month with its Gregorian date, weekday, Fridays and holidays.

Args: year: Jalali year, e.g. 1405. month: 1 (Farvardin) to 12 (Esfand).

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>",
      "month": "<month>"
    },
    "name": "get_month"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
monthYes

Output Schema

NameRequiredDescriptionDefault
daysYes
yearYes
monthYes
month_nameYesPersian month name.
lunar_statusYesHow sure the lunar holidays of this year are.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety and repeatability profile is covered. The description adds useful behavioral context about what the result set contains (Gregorian equivalents, weekdays, Fridays, holidays). It says nothing about out-of-range input handling, error behavior, or result size for a 31-day month.

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?

Two compact blocks: a content summary followed by per-argument notes, with the resource scoping front-loaded. Every line carries information; the only nit is that the opening sentence is a verbless fragment, which slightly weakens the action framing.

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 simple two-parameter read tool with an output schema and full safety annotations, the description covers what it must: what a call returns and how to format both arguments. The remaining gap is sibling routing – nothing tells the agent when a month listing beats get_holidays or today.

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 is bare integers titled 'Year' and 'Month' – so the description carries the full burden, and it does so meaningfully: it specifies the Jalali calendar, gives an example year (1405), states the 1–12 range and names the boundary months (Farvardin, Esfand), which prevents an agent from passing a Gregorian year or a 0-indexed month. It stops short of stating behavior for invalid values.

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 names a specific resource and scope: every day of a Jalali month, each carrying Gregorian date, weekday, Friday flags and holidays. An agent can tell it returns a per-day calendar listing rather than a single date conversion. It does not, however, distinguish itself from siblings such as get_holidays or count_workdays, even though it also surfaces holiday data.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. An agent must infer that get_month is for full-month listings while get_holidays, is_holiday, count_workdays and today serve narrower questions. The parameter range hints at scope but is not usage routing.

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