Skip to main content
Glama

AstroWay Astrology API (full catalogue)

Regional calendar: month boundaries for a year

astroway_vedic_calendar_regional_months
Read-onlyIdempotent

Month boundaries of a regional calendar for the year. Solar: tamil (sankranti before sunset: that day), malayalam (within the first three fifths of daylight: that day), bengali (between sunrise and midnight: the next day; after midnight: the day after), each month with its sankranti moment, first and last civil day, length and year (Tamil samvatsara, Kollam era, Bangabda). Lunisolar: gujarati (amanta, Vikram Samvat from Kartika, Sud and Vad) and marathi (amanta, Shaka from Chaitra), each month with its new moons, first and last civil day, adhika and kshaya.

[Group: Vedic] [Endpoint: POST /v1/vedic/calendar/regional/months] [Required: calendar, year, latitude, longitude] [Cost: 50 credits (Tier 3)]

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>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "astroway_vedic_calendar_regional_months"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesGregorian year, 1900 to 2100. Entries are those whose date falls in this year.
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
ayanamsaNoSidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
calendarYestamil, malayalam, bengali (solar months from the sankranti by each region's rule), gujarati (amanta, Vikram Samvat from Kartika), marathi (amanta, Shaka from Chaitra).
latitudeYesLatitude in decimal degrees, north positive. Between -66 and 66: further out the Sun does not rise on some days and a Hindu day has no start.
timezoneNoIANA zone name such as Asia/Kolkata, America/New_York or Europe/Kyiv, or auto (default) to look it up from the coordinates. Resolved day by day: each day is read on the offset that zone kept that day, so summer time is followed.
longitudeYesLongitude in decimal degrees, east positive.
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
ayanamsaIdNo
timezoneOffsetNoA fixed offset in hours instead of a zone, for the whole year. Ignored when timezone is sent.

Output Schema

NameRequiredDescriptionDefault
ruleNo
yearNo
placeNo
monthsNo
calendarNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real domain behavior (per-region sankranti cut-offs, adhika/kshaya months, era naming), which is valuable, but it says nothing about cost/credits, geographic limits on latitude, or why coordinates are required — the latitude restriction only appears in the schema.

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?

Front-loaded with purpose, then a compact Solar/Lunisolar split with clear per-region clauses and no filler. Dense but every clause carries information; a bulleted or line-broken layout would read slightly better.

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

Completeness5/5

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

With annotations covering safety, an output schema covering returns, and a 90%-covered input schema, the description supplies the one thing structured fields cannot: the regional boundary rules and what fields each month entry carries. Nothing an agent needs to invoke it correctly is missing.

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 90% and documents year range, calendar enum meanings, latitude bounds and timezone resolution in detail. The description's calendar parenthetical largely duplicates the enum description, so it adds little parameter meaning beyond the schema; 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?

States a specific verb+resource ('month boundaries of a regional calendar for the year') and enumerates the five supported calendars with what each entry contains, so an agent knows exactly what is produced. It never names the closely related siblings (astroway_vedic_calendar_months, astroway_vedic_calendar_regional_date), so the differentiation is only implicit.

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 'for the year' and by the inclusion of latitude/longitude in the required set, but there is no explicit when-to-use or when-not, and no routing to the single-date regional_date tool or the general months tool. The agent must infer the choice from the tool name and schema.

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