Skip to main content
Glama

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

Today in other calendars

today
Read-onlyIdempotent

Today's date in a time zone, in the Hebrew, Islamic, Chinese and other calendars. 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": "today"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoCalendars to return, comma-separated (gregorian, hebrew, islamic, chinese, persian, indian, ethiopian, coptic) or "all". Default: gregorian,hebrew,islamic,chinese.
methodNoIslamic method: umalqura (default, Saudi Arabia's official calendar), civil or tabular.
timezoneNoIANA time zone, e.g. America/New_York, Asia/Jerusalem (default UTC).
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

B3/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. Beyond that the description adds no behavioral context: it does not mention that afterSunset rolls Hebrew/Islamic days forward, nor that method only affects the Islamic result. The second sentence is promotional and contributes nothing behavioral.

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

Conciseness2/5

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

The first sentence is front-loaded and efficient, but the trailing 'More APIs from FitzTopPicks' sentence with UTM tracking parameters is pure marketing that does not help an agent select or invoke the tool, diluting an otherwise tight definition.

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 simple, zero-required-parameter read tool with full schema coverage and no output schema, the description is adequate to identify the tool. It falls short on disambiguating from convert_date and on noting how afterSunset and timezone interact with the result.

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 100%, so all four parameters (to, method, timezone, afterSunset) are fully documented in the schema, including enum values and defaults. The description repeats only the calendar names and adds no syntax or format detail beyond that, so baseline 3 applies.

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?

A specific verb+resource: returns today's date in a given time zone rendered in multiple calendars. It is clearly distinguishable from the sibling convert_date, which converts a supplied date, though the description never makes that distinction explicit.

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 only implied by the title and first sentence: fetch today's date rather than converting an arbitrary one. There is no explicit statement of when to prefer this over convert_date, nor any note that timezone defaults to UTC and can shift the date.

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