AstroWay Vedic astrology

Hindu calendar: lunar months, adhika and kshaya, eras

astroway_vedic_calendar_months

Read-onlyIdempotent

The lunar months touching the year: new moon, full moon, next new moon, the Sun's sidereal sign at the opening new moon, adhika (no sankranti inside) and kshaya (two), and the purnimanta names of both pakshas. Plus the twelve sankrantis with their local moments and the eras: Shaka and Vikram Samvat from Chaitra, Vikram Samvat from Kartika (Gujarat), the sixty-year samvatsara name. 2026 has Adhika Jyeshtha (17 May to 15 June).

[Group: Vedic] [Endpoint: POST /v1/vedic/calendar/months] [Required: 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": {
      "year": "<year>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "astroway_vedic_calendar_months"
  }
}

Input Schema

Name	Required	Description
`year`	Yes	Gregorian year, 1900 to 2100. Entries are those whose date falls in this year.
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`ayanamsa`	No	Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
`latitude`	Yes	Latitude 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.
`timezone`	No	IANA 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.
`longitude`	Yes	Longitude in decimal degrees, east positive.
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`ayanamsaId`	No
`timezoneOffset`	No	A fixed offset in hours instead of a zone, for the whole year. Ignored when timezone is sent.

Output Schema

Name	Required	Description	Default
`eras`	No
`rule`	No
`year`	No
`place`	No
`adhika`	No
`kshaya`	No
`months`	No
`sankrantis`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.5/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, so the safety profile needs no restating. The description adds a genuine behavioral nuance by framing results as months 'touching the year' (boundary months included) and giving local moments for sankrantis, which implies coordinate/timezone dependence. It says nothing about response size, pagination, or how adhika/kshaya interleaving affects ordering.

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?

Three sentences, front-loaded with the payload contents, then sankrantis and eras, then a concrete example. The opening sentence is a dense comma-list of jargon, which is less scannable than it could be, but no sentence is padding.

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 an output schema present, the description need not explain return values, and annotations cover the safety profile; what remains is making the domain jargon intelligible, which the parenthetical glosses for adhika ('no sankranti inside') and kshaya ('two') accomplish. It is complete enough to call correctly, though a one-line pointer to the regional-months sibling would close the remaining gap.

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 89%, so the schema already explains year bounds, latitude limits, timezone resolution and the compact-mode fields. The description adds no parameter-level detail beyond implicitly requiring a location for 'local moments'. Baseline 3 applies when the schema does the heavy lifting.

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 a precise resource — lunar months of a year with their new/full moon boundaries, adhika/kshaya flags, purnimanta paksha names — plus the twelve sankrantis and the Shaka/Vikram Samvat and samvatsara eras. That is far more specific than the title alone and lets an agent know exactly what data comes back. It stops short of naming how it differs from close siblings such as astroway_vedic_calendar_regional_months or astroway_calendar_lunar_calendar.

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 content ('the lunar months touching the year'), but there is no explicit when-to-use statement, no prerequisites, and no routing to or away from the regional-months, festivals, or ICS siblings. The worked example '2026 has Adhika Jyeshtha (17 May to 15 June)' hints at the intended question shape without stating it.

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

All AstroWay Vedic astrology tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?