Vedic Astrology and Kundli MCP Server by RoxyAPI

Get planetary aspects (Drishti) - Mutual aspects between all planets

post_vedic_astrology_aspects

Read-only

Calculate all planetary aspects (Drishti) for a given time. Returns full aspects (7th house for all planets) and special aspects (Mars 4th/8th, Jupiter 5th/9th, Saturn 3rd/10th). Includes aspect table grouped by planet, mutual aspects, and individual aspect details with orb calculation. Essential for birth chart analysis, compatibility checking, and transit predictions. Planetary aspects API, drishti calculator, vedic astrology aspects, graha drishti.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes	Date in YYYY-MM-DD format. Planetary positions are calculated for this date to determine mutual aspects (drishti).
`time`	Yes	Time in HH:MM:SS format (24-hour). Exact time affects fast-moving planets (Moon, Mercury) and aspect orbs.
`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. Used for Lagna calculation which affects house-based aspect analysis.
`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).
`longitude`	Yes	Observer longitude in decimal degrees. Affects local sidereal time for positional calculations.
`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
`aspects`	Yes
`planets`	Yes
`datetime`	Yes
`aspectTable`	Yes
`mutualAspects`	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": {
+    "aspectTable": {
+      "items": {
+        "properties": {
+          "aspects": {
+            "items": {
+              "properties": {
+                "aspectType": {
+                  "type": "string"
+                },
+                "planet": {
+                  "type": "string"
+                },
+                "strength": {
+                  "type": "number"
+                }
+              },
+              "required": [
+                "planet",
+                "aspectType",
+                "strength"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "planet": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "planet",
+          "aspects"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "aspects": {
+      "items": {
+        "properties": {
+          "aspectType": {
+            "enum": [
+              "conjunction",
+              "7th",
+              "4th",
+              "8th",
+              "5th",
+              "9th",
+              "3rd",
+              "10th"
+            ],
+            "type": "string"
+          },
+          "aspectedPlanet": {
+            "type": "string"
+          },
+          "aspectingPlanet": {
+            "type": "string"
+          },
+          "orb": {
+            "type": "number"
+          },
+          "strength": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "aspectingPlanet",
+          "aspectedPlanet",
+          "aspectType",
+          "strength",
+          "orb"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "datetime": {
+      "type": "string"
+    },
+    "mutualAspects": {
+      "items": {
+        "properties": {
+          "aspectType": {
+            "type": "string"
+          },
+          "planet1": {
+            "type": "string"
+          },
+          "planet2": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "planet1",
+          "planet2",
+          "aspectType"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "planets": {
+      "items": {
+        "properties": {
+          "longitude": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "sign": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "longitude",
+          "sign"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "datetime",
+    "planets",
+    "aspects",
+    "aspectTable",
+    "mutualAspects"
+  ],
+  "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: +[
+  {
+    "date": "2026-02-03",
+    "latitude": 17.385044,
+    "longitude": 78.486671,
+    "time": "12:00:00"
+  }
+]

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

A4/5.0

Behavior4/5

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

Even with readOnlyHint=true and destructiveHint=false in annotations, the description adds meaningful behavioral detail: it states the tool 'Returns full aspects...', includes a table, mutual aspects, and 'individual aspect details with orb calculation.' This goes beyond the annotation safety profile, though it does not cover edge behaviors like error conditions or rate limits.

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 core description is front-loaded with the primary purpose, but the final sentence is a keyword block ('Planetary aspects API, drishti calculator, vedic astrology aspects, graha drishti') that adds no functional information and is noise for an agent. This bloat prevents a higher score.

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 presence of an output schema, full parameter descriptions, and annotations covering read-only safety, the description covers the essential use context and key output contracts (full vs. special aspects, orb calculation). It is complete enough for an agent to invoke correctly, though it omits any mention of coordinate system or timezone handling, which are already documented in 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?

Input schema coverage is 100%, with all seven parameters fully described, so the description is not required to repeat them. It refers to 'a given time' and the aspect calculation but adds no parameter-specific meaning beyond the schema. Baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'Calculate all planetary aspects (Drishti) for a given time.' It further distinguishes its scope by enumerating full 7th-house aspects and special aspects for Mars, Jupiter, and Saturn, which clearly separates it from sibling tools like aspects_lunar and aspects_monthly that target narrower subsets.

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 provides clear usage context by stating it is 'Essential for birth chart analysis, compatibility checking, and transit predictions.' However, it does not explicitly name alternatives or state when not to use this tool versus related aspect endpoints such as post_vedic_astrology_aspects_lunar.

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?