Skip to main content
Glama

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

Months of a year

calendar_months
Read-onlyIdempotent

Every month of a year in one calendar with its first and last Gregorian day and length (Hebrew leap years and Adar II, Chinese leap months, Islamic methods, Persian, Indian, Ethiopian and Coptic months). More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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": {
      "calendar": "<calendar>",
      "year": "<year>"
    },
    "name": "calendar_months"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesThe year in that calendar (e.g. Hebrew 5787, Islamic 1448, Persian 1405).
methodNoIslamic method: umalqura (default, Saudi Arabia's official calendar), civil or tabular.
calendarYesThe calendar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral detail beyond that: leap-month handling (Hebrew Adar II, Chinese leap months) and variant Islamic methods, which tells the agent to expect calendar-specific month counts rather than a flat 12-item list.

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 first sentence is front-loaded and information-dense but crammed into one long parenthetical. The second sentence is a promotional URL for 'More APIs from FitzTopPicks' that gives the agent no selection or invocation value.

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?

With no output schema, the description must convey the return shape, and it does: month entries carrying first/last Gregorian day and length. All three parameters are fully documented in the schema, so the only gaps are output ordering and naming conventions.

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 coverage is 100% and the schema already explains `calendar`, `year` (with per-calendar examples) and the `method` enum. The description's references to Islamic methods and leap years restate what the schema documents, adding little parameter-level meaning, so this sits at the baseline.

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 names the resource ('every month of a year in one calendar') and lists the payload precisely (first and last Gregorian day and length), which is far more specific than the title 'Months of a year'. It never contrasts itself with siblings such as list_calendars or convert_date, so the agent must infer the boundary.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of an alternative. The agent is left to guess whether this or list_calendars/convert_date is the right call for a given calendar question.

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