Skip to main content
Glama
jalali-calendar-mcp

jalali-calendar-mcp

Today in Iran

today
Read-onlyIdempotent

Get the current date in Iran in both Jalali and Gregorian formats, plus a clear indication of whether it is an official day off.

Instructions

Today's date in Iran (Asia/Tehran), Jalali and Gregorian, and whether it is a day off.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "today"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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.7/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 profile is fully covered by structured data. The description's added value is limited to naming the timezone and the dual-calendar plus day-off payload, which is largely restated by the output schema. It adds no operational context such as how 'day off' is determined (official holidays vs. weekends).

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?

A single front-loaded sentence with no filler; the timezone qualifier and the two calendars plus day-off flag all earn their place. Nothing is repeated and there is no preamble.

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 zero-parameter, read-only tool with an output schema already declared, the description covers what is returned and in which timezone. The only soft gap is what 'day off' means (official holidays, weekend definition), which an agent might need to interpret results correctly.

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?

The tool takes zero parameters, so the schema leaves nothing to interpret and the baseline for a parameter-free tool is 4. The description correctly signals that no input is needed by framing the result entirely around 'today'.

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 resource and scope: today's date in Iran (Asia/Tehran), returned in both Jalali and Gregorian, plus day-off status. That distinguishes it from siblings like convert_date and get_holidays by making clear it takes no input and is anchored to 'today'. It stops short of explicitly naming the alternatives it displaces.

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 name and the 'Today's date' framing — an agent can infer it should call this instead of convert_date when it needs the current date. However, there is no explicit when-to-use/when-not statement, no pointer to convert_date for arbitrary dates, and no mention of is_holiday for checking a specific date.

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