Vedic Astrology and Kundli MCP Server by RoxyAPI

Monthly Transit - Planetary sign changes for an entire month

post_vedic_astrology_transit_monthly

Read-only

Get all planetary sign (rashi) changes for a given month. Shows when each planet transitions from one zodiac sign to another. Covers all 9 Vedic planets: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu, Ketu. Includes starting positions at the beginning of the month. Omit year and month to get the month in progress, so a published gochar calendar stays current without a redeploy. Essential for transit prediction, monthly horoscope generation, and muhurta planning. Monthly planetary transit API, gochar calendar, rashi parivartan dates.

Input Schema

TableJSON 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 transit analysis (1900-2100). Defaults to the current year (UTC).
`month`	No	Month number (1-12) for transit analysis. 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.
`timezone`	No	Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved once, at the start of the window, and that offset applies to every time in the response. Output times are converted to this timezone. Defaults to 0 (UTC).
`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

TableJSON Schema

Name	Required	Description	Default
`year`	Yes
`month`	Yes
`timezone`	Yes
`transitEvents`	Yes
`startingPositions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 23, 2026

changedInput schema / properties / timezone / description

Previous value: -"Timezone offset from UTC in hours. Output times are converted to this timezone. Defaults to 0 (UTC)."New value: +"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved once, at the start of the window, and that offset applies to every time in the response. Output times are converted to this timezone. Defaults to 0 (UTC)."

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "month": {
+      "type": "number"
+    },
+    "startingPositions": {
+      "items": {
+        "properties": {
+          "longitude": {
+            "type": "number"
+          },
+          "planet": {
+            "type": "string"
+          },
+          "planetLocalized": {
+            "type": "string"
+          },
+          "sign": {
+            "type": "string"
+          },
+          "signLocalized": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "planet",
+          "sign",
+          "longitude"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "timezone": {
+      "type": "number"
+    },
+    "transitEvents": {
+      "items": {
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "datetime": {
+            "type": "string"
+          },
+          "fromSign": {
+            "type": "string"
+          },
+          "fromSignLocalized": {
+            "type": "string"
+          },
+          "isRetrograde": {
+            "type": "boolean"
+          },
+          "planet": {
+            "type": "string"
+          },
+          "planetLocalized": {
+            "type": "string"
+          },
+          "time": {
+            "type": "string"
+          },
+          "toSign": {
+            "type": "string"
+          },
+          "toSignLocalized": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "planet",
+          "fromSign",
+          "toSign",
+          "date",
+          "time",
+          "datetime",
+          "isRetrograde"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "year": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "year",
+    "month",
+    "timezone",
+    "startingPositions",
+    "transitEvents"
+  ],
+  "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 transit analysis."New value: +"Month number (1-12) for transit analysis. Defaults to the current month (UTC)."

changedInput schema / properties / year / description

Previous value: -"Year for monthly transit analysis (1900-2100)."New value: +"Year for monthly transit analysis (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"
+}

Changed1 schema field changedJul 12, 2026

changedInput schema / properties / timezone / anyOf

Previous value: -[
-  {
-    "maximum": 14,
-    "minimum": -14,
-    "type": "number"
-  },
-  {
-    "pattern": "^[A-Za-z_]+(?:\\/[A-Za-z0-9_+-]+){0,2}$",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 14,
+    "minimum": -14,
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]

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 declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds behavioral context beyond annotations: it includes starting positions at the beginning of the month, and the defaulting behavior when omitting year/month ('Omit year and month to get the month in progress') which explains a non-obvious aspect. It does not describe response structure or potential edge cases, but the output schema covers that. No contradiction with annotations.

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 description is mostly efficient, front-loading the core purpose and enumerating planets. However, it ends with a keyword-dump sentence: 'Monthly planetary transit API, gochar calendar, rashi parivartan dates.' This adds no value and feels like SEO padding, making it less concise than it could be. Overall it is not overly long, but the redundant tail pulls the score down from a 4.

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?

Given the output schema exists and annotations cover safety, the description is comprehensive for an agent to decide when to call it and what to expect. It covers scope (all 9 planets), includes starting positions, and explains the defaulting behavior. It does not mention timezone or coordinate system nuances, but those are thoroughly described in the schema. The main gap is not explicitly routing to sibling tools for related but different use cases, but the core information is complete.

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 all six parameters are documented in the schema. The description adds a practical note about omitting year and month to get the current month, which reiterates schema defaults but also highlights a specific usage pattern. It does not provide additional syntax or format details beyond the schema, so a baseline of 3 is appropriate—the schema does the heavy lifting.

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?

The description clearly states the tool's purpose: 'Get all planetary sign (rashi) changes for a given month.' It specifies the resource (planetary sign changes) and the timeframe (month), and distinguishes itself from sibling tools by emphasizing transitions ('Shows when each planet transitions from one zodiac sign to another') and listing all 9 Vedic planets. This makes it unambiguous what the tool does relative to others like post_vedic_astrology_transit (point-in-time) or planetary_positions_monthly (positions vs. changes).

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?

The description provides explicit usage guidance: 'Omit year and month to get the month in progress, so a published gochar calendar stays current without a redeploy.' It also states the tool is 'Essential for transit prediction, monthly horoscope generation, and muhurta planning,' giving clear contexts. However, it does not explicitly contrast with alternatives or state when not to use it (e.g., for a single day's transit), so it falls short of a 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?