Skip to main content
Glama
jalali-calendar-mcp

jalali-calendar-mcp

Convert a date (Jalali / Gregorian)

convert_date
Read-onlyIdempotent

Convert dates between Jalali (Persian) and Gregorian calendars using a single YYYY-MM-DD or YYYY/MM/DD value.

Instructions

Convert a date between the Jalali (Persian) and Gregorian calendars.

Args: value: Gregorian YYYY-MM-DD or Jalali YYYY/MM/DD (Persian digits are fine; any year below 1700 is Jalali).

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

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

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety and determinism are covered. The description adds real behavioral context beyond them: Persian digits are accepted, both accepted input layouts are given, and the ambiguity of calendar detection is resolved by the year<1700 rule. It does not mention error behavior for invalid or unparseable dates.

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 front-loaded sentence establishes purpose, followed by a compact Args block whose content is entirely substantive format rules. There is no filler or repeated restatement of the title.

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 converter with annotations covering side effects and an output schema covering the return value, the definition supplies what the agent needs to call it correctly. The only omissions are edge-case behavior, such as what happens with malformed input or out-of-range years.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, and it does: it names the argument, gives the exact Gregorian YYYY-MM-DD and Jalali YYYY/MM/DD formats, permits Persian digits, and states the disambiguation rule. Nothing needed to construct a valid call is left to inference.

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?

States a specific verb (convert) and resource (a date) plus the two calendars involved (Jalali/Persian and Gregorian), so the agent can identify this as the conversion tool without opening the schema. It is clearly distinct from the surrounding date utilities like today, get_month, or count_workdays.

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 rather than stated: the input format determines direction, and the description explains the year-below-1700 heuristic for auto-detecting Jalali. There is no explicit 'use this instead of X' routing or statement of when not to use it, though for a single-purpose converter that guidance is largely self-evident.

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