Vedic Astrology and Kundli MCP Server by RoxyAPI

Transit Analysis - Compare current planets to natal chart (Gochar)

post_vedic_astrology_transit

Read-only

Analyze planetary transits (Gochar) over natal chart positions. Each transiting graha comes back with TWO whole-sign house numbers, because the two readings answer different questions: houseFromMoon is counted from the natal Moon sign (Janma Rashi), which is the reference classical Gochara uses, and natalHouse is counted from the Lagna. Also returns graha drishti onto the natal grahas (7th for every graha, plus Mars 4th and 8th, Jupiter 5th and 9th, Saturn 3rd and 10th), degree-based angular aspects with orbs, the Gochara Kaksha verdict, and highlighted transits from the slow-moving grahas (Jupiter, Saturn, Rahu, Ketu). Essential for timing predictions, event forecasting, and understanding current planetary influences. Transit analysis API, gochar calculator, vedic transit predictions, Chandra Lagna gochara, graha drishti.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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.
`latitude`	Yes	Observer latitude in decimal degrees. Determines Placidus house cusps for natal chart house assignments.
`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 to the offset in force at the given date and time. Defaults to 5.5 (IST).
`birthDate`	Yes	Birth date in YYYY-MM-DD format. Used to calculate the natal chart against which transits are analyzed.
`birthTime`	Yes	Birth time in HH:MM:SS format (24-hour). Critical for accurate natal Lagna and Placidus house cusps which determine transit house placements.
`longitude`	Yes	Observer longitude in decimal degrees. Affects local sidereal time for Lagna and house calculations.
`transitDate`	Yes	Transit date to analyze in YYYY-MM-DD format. Planetary positions on this date are overlaid on the natal chart.
`transitTime`	No	Transit time in HH:MM:SS format (24-hour). Affects fast-moving planets like Moon. Defaults to noon.
`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
`frame`	Yes
`keyTransits`	Yes
`natalPlanets`	Yes
`birthDatetime`	Yes
`transitDatetime`	Yes
`transitingPlanets`	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. Defaults to 5.5 (IST)."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 to the offset in force at the given date and time. Defaults to 5.5 (IST)."

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "birthDatetime": {
+      "type": "string"
+    },
+    "frame": {
+      "properties": {
+        "ayanamsa": {
+          "type": "string"
+        },
+        "ayanamsaDegrees": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "ayanamsa",
+        "ayanamsaDegrees"
+      ],
+      "type": "object"
+    },
+    "keyTransits": {
+      "items": {
+        "properties": {
+          "aspects": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "description": {
+            "type": "string"
+          },
+          "drishti": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "houseFromMoon": {
+            "type": "number"
+          },
+          "natalHouse": {
+            "type": "number"
+          },
+          "planet": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "planet",
+          "description",
+          "natalHouse",
+          "houseFromMoon",
+          "aspects",
+          "drishti"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "natalPlanets": {
+      "items": {
+        "properties": {
+          "house": {
+            "type": "number"
+          },
+          "longitude": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "sign": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "longitude",
+          "sign",
+          "house"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "transitDatetime": {
+      "type": "string"
+    },
+    "transitingPlanets": {
+      "items": {
+        "properties": {
+          "aspectsToNatal": {
+            "items": {
+              "properties": {
+                "aspectType": {
+                  "type": "string"
+                },
+                "natalPlanet": {
+                  "type": "string"
+                },
+                "orb": {
+                  "type": "number"
+                }
+              },
+              "required": [
+                "natalPlanet",
+                "aspectType",
+                "orb"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "drishtiToNatal": {
+            "items": {
+              "properties": {
+                "aspectType": {
+                  "enum": [
+                    "conjunction",
+                    "7th",
+                    "4th",
+                    "8th",
+                    "5th",
+                    "9th",
+                    "3rd",
+                    "10th"
+                  ],
+                  "type": "string"
+                },
+                "natalPlanet": {
+                  "type": "string"
+                },
+                "orb": {
+                  "type": "number"
+                },
+                "strength": {
+                  "type": "number"
+                }
+              },
+              "required": [
+                "natalPlanet",
+                "aspectType",
+                "strength",
+                "orb"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "houseFromMoon": {
+            "type": "number"
+          },
+          "kaksha": {
+            "properties": {
+              "bindu": {
+                "type": [
+                  "boolean",
+                  "null"
+                ]
+              },
+              "binduCount": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "endDegree": {
+                "type": "number"
+              },
+              "lord": {
+                "type": "string"
+              },
+              "number": {
+                "type": "number"
+              },
+              "startDegree": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "number",
+              "lord",
+              "startDegree",
+              "endDegree",
+              "bindu",
+              "binduCount"
+            ],
+            "type": "object"
+          },
+          "longitude": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "natalHouse": {
+            "type": "number"
+          },
+          "sign": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "longitude",
+          "sign",
+          "natalHouse",
+          "houseFromMoon",
+          "aspectsToNatal",
+          "drishtiToNatal",
+          "kaksha"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "frame",
+    "birthDatetime",
+    "transitDatetime",
+    "natalPlanets",
+    "transitingPlanets",
+    "keyTransits"
+  ],
+  "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 17, 2026

addedInput schema / examples

Added value: +[
+  {
+    "birthDate": "1990-07-04",
+    "birthTime": "10:12:00",
+    "latitude": 17.385044,
+    "longitude": 78.486671,
+    "transitDate": "2026-02-03"
+  }
+]

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."

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

A3.9/5.0

Behavior5/5

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

With readOnlyHint and destructiveHint already covering safety, the description adds valuable behavioral detail: the distinction between houseFromMoon and natalHouse, the exact drishti rules per graha, the Kaksha verdict, and inclusion of slow-moving transits. This goes well beyond what annotations express.

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?

The substantive sentences are front-loaded and information-dense, especially the house-number and drishti explanations. The final keyword-style sentence ('Transit analysis API, gochar calculator...') repeats already-stated concepts and adds noise, preventing a 5.

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?

For a 9-parameter tool with an output schema and read-only annotations, the description is largely complete: purpose, use cases, and key return semantics are all present. The sibling differentiation gap and the slight mismatch between 'current planets' in the title and the arbitrary transitDate input keep this from being fully 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?

The input schema has 100% description coverage, so the baseline applies and the description does not need to repeat parameter details. It adds no parameter-specific semantics; the house and drishti discussion concerns output interpretation rather than how to fill inputs.

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 opening sentence names an explicit action and resource ('Analyze planetary transits (Gochar) over natal chart positions'), so an agent understands the core function immediately. It does not explicitly differentiate from the sibling post_vedic_astrology_transit_monthly, which is the closest alternative.

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?

The description says the tool is 'Essential for timing predictions, event forecasting, and understanding current planetary influences,' which gives context. However, it does not name transit_monthly or any sibling as the alternative for date-range analysis, nor does it state when not to use this tool.

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?