Vedic Astrology and Kundli MCP Server by RoxyAPI

Monthly Ephemeris - Daily sidereal planetary positions for a month

post_vedic_astrology_planetary_positions_monthly

Read-only

Get daily sidereal ecliptic positions for all 9 Vedic planets (Navagraha) for an entire month. Returns longitude, zodiac sign, degree within sign, and retrograde status for each planet on each day. Calculated at noon UTC. Omit year and month to get the month in progress, so a published ephemeris page stays current without a redeploy. Essential for ephemeris generation, transit tracking, and planetary movement visualization. Monthly planetary ephemeris API, sidereal position table, daily graha gochara positions, ecliptic longitude calculator. Rahu and Ketu are the mean lunar node, referred to the true equinox of date, with Ketu exactly opposite Rahu.

Input Schema

Name	Required	Description	Default
`lang`	No	Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English.	en
`year`	No	Year for monthly ephemeris (1551 to 2649). Defaults to the current year (UTC).
`month`	No	Month number (1-12) for ephemeris. Defaults to the current month (UTC).
`compact`	No	Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
`coordinateSystem`	No	Coordinate system for longitude output. "sidereal" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. "tropical" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to "sidereal".	sidereal

Output Schema

Name	Required	Description	Default
`days`	Yes
`year`	Yes
`month`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 30, 2026

changedInput schema / properties / year / description

Previous value: -"Year for monthly ephemeris (1900-2100). Defaults to the current year (UTC)."New value: +"Year for monthly ephemeris (1551 to 2649). Defaults to the current year (UTC)."

changedInput schema / properties / year / maximum
```
Previous value: -2100New value: +2649
```
changedInput schema / properties / year / minimum
```
Previous value: -1900New value: +1551
```

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "days": {
+      "items": {
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "positions": {
+            "items": {
+              "properties": {
+                "degreeInSign": {
+                  "type": "number"
+                },
+                "isRetrograde": {
+                  "type": "boolean"
+                },
+                "longitude": {
+                  "type": "number"
+                },
+                "planet": {
+                  "type": "string"
+                },
+                "planetLocalized": {
+                  "type": "string"
+                },
+                "sign": {
+                  "type": "string"
+                },
+                "signLocalized": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "planet",
+                "longitude",
+                "sign",
+                "degreeInSign",
+                "isRetrograde"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "date",
+          "positions"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "month": {
+      "type": "number"
+    },
+    "year": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "year",
+    "month",
+    "days"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 4, 2026

changedInput schema / properties / coordinateSystem / description

Previous value: -"Coordinate system for longitude output. \"sidereal\" (Nirayana) uses Lahiri ayanamsa - standard for Vedic astrology. \"tropical\" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to \"sidereal\"."New value: +"Coordinate system for longitude output. \"sidereal\" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. \"tropical\" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to \"sidereal\"."

Changed2 schema fields changedAug 25, 2026

changedInput schema / properties / lang / description

Previous value: -"Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English."New value: +"Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English."

changedInput schema / properties / lang / enum

Previous value: -[
-  "en",
-  "tr",
-  "de",
-  "es",
-  "hi",
-  "pt",
-  "fr",
-  "ru"
-]New value: +[
+  "en",
+  "tr",
+  "de",
+  "es",
+  "hi",
+  "pt",
+  "fr",
+  "ru",
+  "zh-Hans",
+  "zh-Hant"
+]

Changed2 schema fields changedAug 17, 2026

addedInput schema / examples
```
Added value: +[
+  {}
+]
```

changedInput schema / properties / compact / description

Previous value: -"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."New value: +"Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {\"__cols\":[names],\"__rows\":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens."

Changed4 schema fields changedAug 8, 2026

addedInput schema / properties / lang

Added value: +{
+  "default": "en",
+  "description": "Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.",
+  "enum": [
+    "en",
+    "tr",
+    "de",
+    "es",
+    "hi",
+    "pt",
+    "fr",
+    "ru"
+  ],
+  "example": "en",
+  "type": "string"
+}

changedInput schema / properties / month / description

Previous value: -"Month number (1-12) for ephemeris."New value: +"Month number (1-12) for ephemeris. Defaults to the current month (UTC)."

changedInput schema / properties / year / description

Previous value: -"Year for monthly ephemeris (1900-2100)."New value: +"Year for monthly ephemeris (1900-2100). Defaults to the current year (UTC)."

removedInput schema / required

Removed value: -[
-  "year",
-  "month"
-]

Changed1 schema field changedJul 22, 2026

changedInput schema / properties / compact / description

Previous value: -"Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false."New value: +"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."

Changed1 schema field changedJul 22, 2026

addedInput schema / properties / compact

Added value: +{
+  "default": false,
+  "description": "Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false.",
+  "type": "boolean"
+}

First observedJul 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish the safe-read profile (readOnlyHint=true, destructiveHint=false), and the description adds genuinely new behavioral facts: sampling at noon UTC, the mean-lunar-node definition of Rahu/Ketu referred to the true equinox of date with Ketu exactly opposite Rahu, and the default-to-current-month behavior. That is substantive disclosure beyond the annotations, though it says nothing about response size or pagination beyond what the schema's compact flag already implies.

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 opening sentences are well front-loaded and information-dense, but the keyword-stuffed clause ('Monthly planetary ephemeris API, sidereal position table, daily graha gochara positions, ecliptic longitude calculator') is pure search fodder that adds no operational meaning. Removing it would lose nothing for an agent, so structure is penalized.

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, return-value documentation is not required, yet the description still frames the payload shape and adds the astronomical conventions an agent needs to interpret the numbers correctly. Nothing essential is missing; the only shortfall is that coordinate-system selection semantics are left to the schema.

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 lang, year, month, compact and coordinateSystem are already fully documented in the schema, making 3 the baseline. The description restates the year/month omission default but adds no syntax or interpretation the schema lacks; the coordinateSystem sidereal-vs-tropical tradeoff is left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get daily sidereal ecliptic positions for all 9 Vedic planets') with explicit scope ('for an entire month'), which separates it from the single-date planetary_positions and daily siblings. The returns are enumerated (longitude, sign, degree-in-sign, retrograde status), so an agent knows exactly what it gets without opening the schema.

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?

Gives clear usage context ('essential for ephemeris generation, transit tracking, and planetary movement visualization') and a concrete operational rule ('omit year and month to get the month in progress, so a published ephemeris page stays current without a redeploy'). It stops short of naming an alternative sibling or stating when not to use it, so it lands at 4 rather than 5.

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

All Vedic Astrology and Kundli MCP Server by RoxyAPI 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?