Skip to main content
Glama

WritersLogic business agents

calendar-convert

Convert dates between Gregorian and Hijri (named variants), Hebrew, Persian, Ethiopian; Western and Orthodox Easter — Converts a Gregorian date (or a Hebrew, Persian, Ethiopian or Hijri date) to the other calendars via the runtime's ICU, always naming the Hijri variant (Umm al-Qura, tabular civil, tabular astronomical-epoch, ICU astronomical) and flagging when variants disagree on the day; with mode easter, returns Western (Gregorian computus) and Orthodox (Julian computus, with its Gregorian equivalent) Easter a

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": {
      "mode": "<mode>"
    },
    "name": "calendar-convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoCalendars to convert into; hijri-all returns Umm al-Qura, tabular civil and ICU astronomical (add islamic-tbla explicitly; it differs from civil by its epoch) and fails when they disagree. Default: all non-Hijri plus hijri-all.
dateNoconvert: Gregorian date. Exactly one of date or from.
fromNo
modeYes
yearsNoeaster: Gregorian years.
feastsNoeaster: also list Ash Wednesday, Good Friday, Ascension, Pentecost and other moveable feasts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses meaningful behavior: conversion via the runtime's ICU, always naming the Hijri variant, flagging when variants disagree, and using Gregorian/Julian computus for Easter. It does not describe output shape or error behavior, but for a deterministic conversion tool this is substantial disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the description is a single dense run-on sentence with semicolons and a truncated ending ('Easter a'). It would be clearer if split into mode-specific statements.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with six parameters, a nested from object, and no output schema, the description covers calendars and modes but omits return structure and error behavior. It is adequate but leaves gaps an agent would need to infer.

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

Parameters3/5

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

Schema description coverage is 67%, so the schema already documents several parameters. The description reinforces mode and Hijri-variant behavior but does not add meaning for feasts, years, date, or from beyond what the schema provides; baseline 3 is appropriate.

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 and resource: 'Convert dates between Gregorian and Hijri..., Hebrew, Persian, Ethiopian' and covers both convert and Easter modes. The calendar resource clearly distinguishes it from sibling converters like font-convert, timecode-convert, and unit-convert.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the two modes and what each returns, including that mode easter returns Western and Orthodox Easter dates. It does not explicitly state when not to use the tool or route to a sibling, but the usage context is clear for a conversion utility.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources