AstroWay Astrology API (full catalogue)

Hindu calendar: ICS feed of festivals and vrats

astroway_vedic_calendar_ics

Read-onlyIdempotent

The festivals and vrats of a year for a place as an iCalendar file (text/calendar, RFC 5545): one all-day event per observance, the rule, tithi window, parana and source in the description, a stable UID per festival, date and place. Query: year, latitude, longitude, timezone (IANA or auto), include (festivals, vrats or single vrat types, comma separated; default festivals,vrats), tradition. The key travels in X-Api-Key, so fetch it from your server and serve the file to calendar apps; it is priced as one festivals call.

[Group: Vedic] [Endpoint: GET /v1/vedic/calendar/ics] [Required: year, latitude, longitude] [Cost: 100 credits (Tier 4)]

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_ics"
  }
}

Input Schema

Name	Required	Description	Default
`year`	Yes	Gregorian year; events are those dated in it.
`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.
`include`	No	Comma list: festivals, vrats, or single vrat types (ekadashi, pradosh, sankashti, purnima, amavasya, masik-shivaratri).	festivals,vrats
`latitude`	Yes	Latitude in decimal degrees, north positive.
`timezone`	No	IANA zone name, or auto to look it up from the coordinates. Followed day by day, summer time included.	auto
`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.
`tradition`	No	Whose reckoning decides the day where traditions differ (Rama Navami, Janmashtami).	smarta
`ayanamsaId`	No	Ayanamsa id; 1 is Lahiri.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower — and the description still adds real value: event granularity ('one all-day event per observance'), payload contents (rule, tithi window, parana, source), UID stability, and the X-Api-Key header requirement plus its 100-credit pricing. It leaves out how the file is actually delivered (raw body vs. base64/URL) and any size or pagination behavior for a 365-event feed.

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?

It front-loads the definition of what is returned before listing the query surface, and every clause (format, event shape, UID, auth, cost) carries information. The prose is a single dense run-on block though, harder to scan than a short bulleted structure would be.

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 carries the burden of describing the return value, and it does so well by specifying the media type, per-event granularity, and embedded fields. Gaps remain around authentication flow mechanics (key acquisition is mentioned but not how to pass on the client side) and the undocumented compact-mode parameters.

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 the schema already carries the meaning of all nine parameters and this is a baseline-3 case. The description repeats the query surface (year, latitude, longitude, timezone, include, tradition) without adding format or default nuance beyond the schema, and it omits `fields`, `precision`, and `ayanamsaId` entirely — the latter two look like inherited generic parameters the description does not reconcile with an ICS feed.

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 specific verb and resource ('The festivals and vrats of a year for a place as an iCalendar file') and pins the output format to `text/calendar`/RFC 5545, which is exactly what distinguishes it from the sibling `astroway_vedic_calendar_festivals` and `astroway_vedic_calendar_vrats` tools. It never names those siblings directly, so the differentiation is inferable rather than explicit.

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?

It gives concrete usage context that no other field supplies: 'fetch it from your server and serve the file to calendar apps', which tells the agent this is a pass-through artifact feed rather than a JSON result to reason over. It stops short of explicit when-not conditions or naming the JSON siblings it should replace.

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

All AstroWay Astrology API (full catalogue) 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?