AstroWay Astrology API (full catalogue)

Panchang: Gowri Panchangam (Gowri Nalla Neram)

astroway_vedic_panchang_gowri

Read-onlyIdempotent

Tamil Gowri Panchangam: the day (sunrise to sunset) and the night (sunset to next sunrise) each cut into 8 equal segments named by the weekday table (Amirdha, Uthi, Laabam, Dhanam, Sugam good; Rogam, Soram, Visham bad), plus nallaNeram, the good segments with neighbours merged. Checked against drikpanchang Chennai and Delhi.

[Group: Vedic] [Endpoint: POST /v1/vedic/panchang/gowri] [Required: date, latitude, longitude] [Cost: 20 credits (Tier 2)]

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": {
      "date": "<date>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "astroway_vedic_panchang_gowri"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	Civil date, YYYY-MM-DD. The day runs from its sunrise to the next sunrise.
`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
`timezone`	No	IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
`longitude`	Yes
`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	Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

Output Schema

Name	Required	Description	Default
`day`	No
`date`	No
`night`	No
`method`	No
`source`	No
`sunset`	No
`sunrise`	No
`weekday`	No
`nallaNeram`	No
`nextSunrise`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), and the description adds real context beyond them: segments are derived from sunrise/sunset at the supplied coordinates, the weekday table is fixed, nallaNeram merges neighbouring good segments, results were cross-checked against drikpanchang for Chennai and Delhi, and the call costs 20 credits at Tier 2.

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?

One dense but front-loaded sentence gives the definition first, followed by the validation note and compact metadata lines for group, endpoint, required params and cost. No sentence is padding, though the weekday-name list makes it slightly long for a definition.

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?

An output schema exists, so return values need not be explained, and the description supplies the domain logic an agent needs: equal 8-way division of both day and night, the fixed weekday naming table, the good/bad classification, and the nallaNeram derivative. With required params and cost listed, nothing critical is missing for a 9-param read-only computation.

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 67%, so the schema already documents date, timezone, ayanamsa, fields and precision. The description adds only the implicit link that latitude/longitude determine the sunrise/sunset anchors used to cut the day, and says nothing about timezone or offset handling that the schema itself covers.

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 resource (Gowri Panchangam) and concretely describes the output: day and night each split into 8 equal segments named from the weekday table, with good/bad classification and a merged nallaNeram view. It is clearly not a chart or general panchang tool, but it never names or contrasts the nearest siblings (choghadia, hora, rahu_kaal), so differentiation is left to the name.

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 rather than stated: the 'Tamil' qualifier signals a regional variant, and the good/bad segment enumeration implies selecting auspicious windows. There is no explicit when-to-use, when-not-to-use, or pointer to the sibling panchang segment tools that overlap with it.

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?