Skip to main content
Glama

Vedic Astrology and Kundli MCP Server by RoxyAPI

by com.roxyapi
OverviewDiscussionsAdmin

Get KP ruling planets with significators at intervals

post_vedic_astrology_kp_ruling_planets_interval
Read-only

Calculate ruling planets and their KP significators at regular time intervals using Krishnamurti Paddhati prashna (horary) astrology. For each interval, a full Placidus house chart is erected and significators are computed using the 4-level KP hierarchy: Level 1 (strongest) planets in star of house occupant, Level 2 occupants, Level 3 planets in star of house owner, Level 4 house owner. Returns Day Lord (sunrise-based Hindu Vara), Moon Sign/Star/Sub/Sub-Sub Lords, Lagna Sign/Star/Sub/Sub-Sub Lords, unique ruling planets set, and per-ruling-planet house significations. No birth data needed, significators come from each moments sky chart. Use for birth time rectification, muhurta selection, and KP horary number analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoResponse 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
focusNoWhich signification vocabulary the houseThemes map returns. "general" gives the classical bhava significations (self, wealth, siblings, home, and so on). "finance" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use "finance" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to "general".general
compactNoSet 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.
ayanamsaNoAyanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. "kp-old" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. "lahiri" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. "raman" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to "kp-newcomb".kp-newcomb
latitudeYesObserver latitude in decimal degrees
nodeTypeNoLunar 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
timezoneNoTimezone: 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. When non-zero, all datetimes are treated as local time in this timezone (Z suffix is ignored). Output times are also converted to this timezone. Defaults to 5.5 (IST).
longitudeYesObserver longitude in decimal degrees
endDatetimeYesEnd of the interval range in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.
startDatetimeYesStart of the interval range in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.
intervalMinutesYesInterval between calculations in minutes (1-1440). Use 1-5 for birth time rectification.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
focusYes
locationYes
intervalsYes
endDatetimeYes
houseThemesYes
startDatetimeYes
totalIntervalsYes
intervalMinutesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / timezone / description
      Previous value: -"Timezone offset from UTC in decimal hours. When non-zero, all datetimes are treated as local time in this timezone (Z suffix is ignored). Output times are also converted to this timezone. 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 once, at the start of the window, and that offset applies to every time in the response. When non-zero, all datetimes are treated as local time in this timezone (Z suffix is ignored). Output times are also converted to this timezone. Defaults to 5.5 (IST)."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "endDatetime": {
+      "type": "string"
+    },
+    "focus": {
+      "enum": [
+        "general",
+        "finance"
+      ],
+      "type": "string"
+    },
+    "houseThemes": {
+      "additionalProperties": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "type": "object"
+    },
+    "intervalMinutes": {
+      "type": "number"
+    },
+    "intervals": {
+      "items": {
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "datetime": {
+            "type": "string"
+          },
+          "dayLord": {
+            "type": "string"
+          },
+          "lagnaSignLord": {
+            "type": "string"
+          },
+          "lagnaStarLord": {
+            "type": "string"
+          },
+          "lagnaSubSublord": {
+            "type": "string"
+          },
+          "lagnaSublord": {
+            "type": "string"
+          },
+          "moonSignLord": {
+            "type": "string"
+          },
+          "moonSignLordSignifies": {
+            "properties": {
+              "L1": {
+                "items": {
+                  "type": "integer"
+                },
+                "type": "array"
+              },
+              "L2": {
+                "items": {
+                  "type": "integer"
+                },
+                "type": "array"
+              },
+              "L3": {
+                "items": {
+                  "type": "integer"
+                },
+                "type": "array"
+              },
+              "L4": {
+                "items": {
+                  "type": "integer"
+                },
+                "type": "array"
+              }
+            },
+            "required": [
+              "L1",
+              "L2",
+              "L3",
+              "L4"
+            ],
+            "type": "object"
+          },
+          "moonSignifies": {
+            "properties": {
+              "L1": {
+                "items": {
+                  "type": "integer"
+                },
+                "type": "array"
+              },
+              "L2": {
+                "items": {
+                  "type": "integer"
+                },
+                "type": "array"
+              },
+              "L3": {
+                "items": {
+                  "type": "integer"
+                },
+                "type": "array"
+              },
+              "L4": {
+                "items": {
+                  "type": "integer"
+                },
+                "type": "array"
+              }
+            },
+            "required": [
+              "L1",
+              "L2",
+              "L3",
+              "L4"
+            ],
+            "type": "object"
+          },
+          "moonStarLord": {
+            "type": "string"
+          },
+          "moonStarLordSignifies": {
+            "properties": {
+              "L1": {
+                "items": {
+                  "type": "integer"
+                },
+                "type": "array"
+              },
+              "L2": {
+                "items": {
+                  "type": "integer"
+                },
+                "type": "array"
+              },
+              "L3": {
+                "items": {
+                  "type": "integer"
+                },
+                "type": "array"
+              },
+              "L4": {
+                "items": {
+                  "type": "integer"
+                },
+                "type": "array"
+              }
+            },
+            "required": [
+              "L1",
+              "L2",
+              "L3",
+              "L4"
+            ],
+            "type": "object"
+          },
+          "moonSubSublord": {
+            "type": "string"
+          },
+          "moonSublord": {
+            "type": "string"
+          },
+          "moonSublordSignifies": {
+            "properties": {
+              "L1": {
+                "items": {
+                  "type": "integer"
+                },
+                "type": "array"
+              },
+              "L2": {
+                "items": {
+                  "type": "integer"
+                },
+                "type": "array"
+              },
+              "L3": {
+                "items": {
+                  "type": "integer"
+                },
+                "type": "array"
+              },
+              "L4": {
+                "items": {
+                  "type": "integer"
+                },
+                "type": "array"
+              }
+            },
+            "required": [
+              "L1",
+              "L2",
+              "L3",
+              "L4"
+            ],
+            "type": "object"
+          },
+          "rulingPlanets": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "significators": {
+            "items": {
+              "properties": {
+                "planet": {
+                  "type": "string"
+                },
+                "signifies": {
+                  "items": {
+                    "type": "number"
+                  },
+                  "type": "array"
+                }
+              },
+              "required": [
+                "planet",
+                "signifies"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "time": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "date",
+          "time",
+          "datetime",
+          "dayLord",
+          "moonSignLord",
+          "moonStarLord",
+          "moonSublord",
+          "moonSubSublord",
+          "lagnaSignLord",
+          "lagnaStarLord",
+          "lagnaSublord",
+          "lagnaSubSublord",
+          "rulingPlanets",
+          "significators",
+          "moonSignLordSignifies",
+          "moonStarLordSignifies",
+          "moonSublordSignifies",
+          "moonSignifies"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "location": {
+      "properties": {
+        "latitude": {
+          "type": "number"
+        },
+        "longitude": {
+          "type": "number"
+        },
+        "timezone": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "latitude",
+        "longitude",
+        "timezone"
+      ],
+      "type": "object"
+    },
+    "startDatetime": {
+      "type": "string"
+    },
+    "totalIntervals": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "startDatetime",
+    "endDatetime",
+    "intervalMinutes",
+    "location",
+    "totalIntervals",
+    "intervals",
+    "houseThemes",
+    "focus"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • 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"
+]
  4. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "endDatetime": "2026-02-03T01:00:00Z",
+    "intervalMinutes": 5,
+    "latitude": 17.385044,
+    "longitude": 78.486671,
+    "startDatetime": "2026-02-03T00:00:00Z"
+  }
+]
    • 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."
  5. Changed1 schema field changed
    • 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\"."
  6. Changed2 schema fields changed
    • changedInput schema / properties / ayanamsa / description
      Previous value: -"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. Defaults to \"kp-newcomb\"."New value: +"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\"."
    • changedInput schema / properties / ayanamsa / enum
      Previous value: -[
-  "kp-newcomb",
-  "kp-old",
-  "lahiri"
-]New value: +[
+  "kp-newcomb",
+  "kp-old",
+  "lahiri",
+  "raman"
+]
  7. Changed2 schema fields changed
    • addedInput schema / properties / focus
      Added value: +{
+  "default": "general",
+  "description": "Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".",
+  "enum": [
+    "general",
+    "finance"
+  ],
+  "example": "general",
+  "type": "string"
+}
    • 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"
+}
  8. Changed1 schema field changed
    • 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."
  9. Changed1 schema field changed
    • 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"
+}
  10. Changed1 schema field changed
    • 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"
+  }
+]
  11. First observed

TDQS

A4.1/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 meaningful behavioral detail: it explains the KP 4-level hierarchy, the return values (Day Lord, Moon/Lagna lords, ruling planets set, house significations), and notes that 'No birth data needed, significators come from each moments sky chart.' This goes beyond the annotations and gives the agent a clear mental model of the computation.

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 description is a single, dense paragraph that front-loads the core action, then elaborates on the KP hierarchy and outputs. Every sentence contributes: the hierarchy explanation is useful, and the usage note is relevant. It is slightly long but not wasteful, earning a 4 for good structure with no redundancy.

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's complexity (11 params, output schema present), the description covers the essential context: purpose, KP method, output details, and use cases. It does not need to explain return formats since an output schema exists. It could mention the timezone behavior or edge cases, but the schema covers those. Overall, it is adequately complete for an agent to call it correctly.

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 11 parameters are documented in the schema. The description adds minimal parameter-specific value; it only reinforces the intervalMinutes guidance ('Use 1-5 for birth time rectification'), which is already in the schema. Since the schema carries the burden, the description meets the baseline of 3 without adding extra semantic nuance.

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 ruling planets and their KP significators at regular time intervals using Krishnamurti Paddhati prashna (horary) astrology.' It clearly distinguishes from sibling tools like post_vedic_astrology_kp_ruling_planets (single time) and other KP tools by emphasizing the interval aspect, which is also reflected in the tool name.

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 clear usage context: 'Use for birth time rectification, muhurta selection, and KP horary number analysis.' However, it does not explicitly name the alternative single-time tool or state when NOT to use this version, so some inference is needed. It still gives strong contextual guidance.

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 toolsInspect
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