Vedic Astrology and Kundli MCP Server by RoxyAPI

Get KP planetary positions with sub-lords

post_vedic_astrology_kp_planets

Read-only

Get planetary positions with detailed KP star-lord and sub-lord calculations for precise event timing and significator analysis. Returns all 9 planets (Sun through Ketu) with nakshatra, star-lord, sub-lord, and KP horary numbers (1-249). Essential for KP astrology software, significator analysis, and event prediction. Use it as a star lord and sub lord calculator wherever Krishnamurti Paddhati planet positions drive the reading.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes	Birth date in YYYY-MM-DD format
`time`	Yes	Birth time in 24-hour HH:MM:SS format
`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.
`ayanamsa`	No	Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula (most common for KP). "kp-old" uses the Krishnamurti original table. "lahiri" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. "raman" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. "custom" allows providing your own value via ayanamsaValue. Defaults to "kp-newcomb".	kp-newcomb
`latitude`	Yes	Birth location latitude in decimal degrees
`nodeType`	No	Lunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to "mean".	mean
`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) for Vedic astrology.
`longitude`	Yes	Birth location longitude in decimal degrees
`ayanamsaValue`	No	Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`planets`	Yes
`ayanamsa`	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) for Vedic astrology."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) for Vedic astrology."

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "ayanamsa": {
+      "type": "number"
+    },
+    "planets": {
+      "items": {
+        "properties": {
+          "kpNumber": {
+            "type": "number"
+          },
+          "longitude": {
+            "type": "number"
+          },
+          "nakshatra": {
+            "type": "string"
+          },
+          "nakshatraLord": {
+            "type": "string"
+          },
+          "nakshatraNumber": {
+            "type": "number"
+          },
+          "pada": {
+            "type": "number"
+          },
+          "planet": {
+            "type": "string"
+          },
+          "retrograde": {
+            "type": "boolean"
+          },
+          "sign": {
+            "type": "string"
+          },
+          "signLord": {
+            "type": "string"
+          },
+          "starLord": {
+            "type": "string"
+          },
+          "subLord": {
+            "type": "string"
+          },
+          "subSubLord": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "planet",
+          "longitude",
+          "sign",
+          "signLord",
+          "nakshatra",
+          "nakshatraNumber",
+          "nakshatraLord",
+          "pada",
+          "starLord",
+          "subLord",
+          "subSubLord",
+          "kpNumber",
+          "retrograde"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "ayanamsa",
+    "planets"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedAug 17, 2026

addedInput schema / examples

Added value: +[
+  {
+    "date": "1990-07-04",
+    "latitude": 28.6139,
+    "longitude": 77.209,
+    "time": "10:12: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 changedAug 10, 2026

changedInput schema / properties / nodeType / description

Previous value: -"Lunar node type for Rahu and Ketu positions. \"mean\" uses the smooth mean node (traditional Vedic astrology default). \"true\" uses the osculating node with perturbation corrections, oscillating up to 1.5 degrees from mean with a 173-day period. Impacts KP sub-lord assignments in narrow boundary cases. Defaults to \"mean\"."New value: +"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\"."

Changed2 schema fields changedAug 1, 2026

changedInput schema / properties / ayanamsa / description

Previous value: -"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula (most common for KP). \"kp-old\" uses the Krishnamurti original table. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. \"custom\" allows providing your own value via ayanamsaValue. Defaults to \"kp-newcomb\"."New value: +"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula (most common for KP). \"kp-old\" uses the Krishnamurti original table. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. \"custom\" allows providing your own value via ayanamsaValue. Defaults to \"kp-newcomb\"."

changedInput schema / properties / ayanamsa / enum

Previous value: -[
-  "kp-newcomb",
-  "kp-old",
-  "lahiri",
-  "custom"
-]New value: +[
+  "kp-newcomb",
+  "kp-old",
+  "lahiri",
+  "raman",
+  "custom"
+]

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

Behavior3/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 useful behavioral context: it returns all 9 planets, includes nakshatra/star-lord/sub-lord, and KP horary numbers (1-249). However, it doesn't disclose details like the output shape (though an output schema exists), whether the ayanamsa default affects results, or any edge cases around boundary sub-lords. With annotations covering the read-only nature, a 3 is appropriate.

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?

Three sentences with no wasted words. The core purpose is front-loaded, followed by the return contents and use-case framing. The phrase 'Essential for KP astrology software' is slightly promotional but still informative. It earns a 4 rather than 5 because the third sentence partially repeats the second sentence's use-case framing.

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 tool has an output schema, the description doesn't need to explain return values. The description covers what the tool returns, why to use it, and the KP context. It doesn't mention the interval variant (post_vedic_astrology_kp_planets_interval) or how this differs from the cusps tool, but for a single-point-in-time KP planets tool, the description is largely complete. A 4 is fair; a 5 would require explicit sibling differentiation.

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 the schema already documents all 9 parameters thoroughly, including enums, defaults, and examples. The description adds no parameter-specific meaning beyond what the schema provides. Baseline 3 is correct when 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 states a specific verb ('Get') and resource ('planetary positions with detailed KP star-lord and sub-lord calculations'), and clearly distinguishes this tool from siblings like post_vedic_astrology_planetary_positions and post_vedic_astrology_kp_cusps by emphasizing KP sub-lord/star-lord output. It also names the exact planets returned (Sun through Ketu) and the KP horary numbers, making the tool's scope unambiguous.

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 gives clear context for when to use the tool: 'for precise event timing and significator analysis', 'Essential for KP astrology software, significator analysis, and event prediction', and 'Use it as a star lord and sub lord calculator wherever Krishnamurti Paddhati planet positions drive the reading.' It does not explicitly name alternatives or exclusions, but the KP-specific framing implicitly differentiates it from general planetary position tools. A small gap: it doesn't mention when to prefer post_vedic_astrology_kp_planets_interval or post_vedic_astrology_kp_cusps instead.

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?