Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

Convert a date between calendars

convert_date
Read-onlyIdempotent

Convert a date between the Gregorian, Hebrew, Islamic (Hijri), Chinese lunisolar, Persian (Solar Hijri), Indian national, Ethiopian and Coptic calendars. Give a Gregorian "date" (YYYY-MM-DD), or "calendar" with "year", "month" (number or name, e.g. "Kislev", "Ramadan", "Farvardin") and "day". Use it for questions like "what is the Hebrew date of my birthday" or "when is 1 Ramadan 1448 in the Gregorian calendar". More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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

Input Schema

NameRequiredDescriptionDefault
toNoCalendars to return, comma-separated (gregorian, hebrew, islamic, chinese, persian, indian, ethiopian, coptic) or "all". Default: gregorian,hebrew,islamic,chinese.
dayNoDay of the month.
dateNoA Gregorian date, YYYY-MM-DD.
leapNoChinese only: a leap month.
yearNoYear in that calendar.
monthNoMonth number or name.
methodNoIslamic method: umalqura (default, Saudi Arabia's official calendar), civil or tabular.
calendarNoCalendar of year/month/day.
afterSunsetNoTrue when the time is after sunset: Hebrew and Islamic dates move to the next day (their days begin at sunset).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the accepted input shape (either a Gregorian date or calendar+year+month+day), but says nothing about the return format, default output calendars, or error behavior for invalid month names.

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 calendar list and usage examples are front-loaded and each earns its place, but the trailing "More APIs from FitzTopPicks" promotional URL is pure noise for an agent deciding how to call the tool.

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?

With 9 optional parameters and no output schema, the description helpfully resolves the ambiguity of which parameter combination to supply via the two input modes. However, it never describes what a conversion result looks like or which calendars are returned by default, leaving return-shape inference to the schema's `to` default.

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 100%, so baseline is 3, but the description earns an extra point by showing month names across calendars ("Kislev", "Ramadan", "Farvardin"), which clarifies the otherwise ambiguous `month` string field. It does not touch `to`, `method`, `leap`, or `afterSunset`, which rely entirely on the schema.

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 (date) and enumerates the exact eight calendars it handles, so an agent can distinguish it from siblings like list_calendars or calendar_months without opening any schema.

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?

Gives concrete usage contexts ("what is the Hebrew date of my birthday", "when is 1 Ramadan 1448 in the Gregorian calendar") that make the intended trigger obvious, but never names or excludes the sibling tools it should not be used for (e.g. list_calendars, calendar_months).

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