Skip to main content
Glama

Vedic Astrology and Kundli MCP Server by RoxyAPI

Get KP ruling planets with optional significators

post_vedic_astrology_kp_ruling_planets
Read-only

Calculate the 5 ruling planets at any moment using Krishnamurti Paddhati horary astrology. Returns Day Lord, Moon Sign/Star/Sub Lord, Lagna Sign/Star/Sub Lord. Optionally provide birth data (birthDate, birthTime) to include significators showing which houses each ruling planet signifies in the birth chart, which is essential for KP prediction.

Input 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.
datetimeNoISO 8601 datetime (YYYY-MM-DDTHH:MM:SS) for ruling planets. Defaults to current time. Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.
latitudeYesObserver latitude in decimal degrees. Any latitude for the ruling planets alone; with birthDate and birthTime the significators read Placidus cusps, so the latitude must lie below 66.56 degrees north or south and a polar latitude returns 400.
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: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC. An IANA name is resolved to the DST-correct offset of each moment separately: at datetime for the ruling planets, and at birthDate and birthTime for the significators. A decimal is applied to both as sent. Defaults to 5.5.
birthDateNoBirth date (YYYY-MM-DD) to calculate significators. If provided with birthTime, response includes which houses each ruling planet signifies.
birthTimeNoBirth time (HH:MM:SS) for significator calculation. Required if birthDate is provided.
longitudeYesObserver longitude in decimal degrees

Output Schema

NameRequiredDescriptionDefault
focusNo
dayLordYes
datetimeYes
locationYes
houseThemesNo
moonSublordYes
lagnaSublordYes
moonSignLordYes
moonStarLordYes
lagnaSignLordYes
lagnaStarLordYes
rulingPlanetsYes
significatorsNo
moonSubSublordYes
lagnaSubSublordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / latitude / description
      Previous value: -"Observer latitude in decimal degrees"New value: +"Observer latitude in decimal degrees. Any latitude for the ruling planets alone; with birthDate and birthTime the significators read Placidus cusps, so the latitude must lie below 66.56 degrees north or south and a polar latitude returns 400."
    • changedInput schema / properties / timezone / description
      Previous value: -"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC. IANA resolved to the DST-correct offset based on birthDate or datetime. Defaults to 5.5."New value: +"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC. An IANA name is resolved to the DST-correct offset of each moment separately: at datetime for the ruling planets, and at birthDate and birthTime for the significators. A decimal is applied to both as sent. Defaults to 5.5."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "datetime": {
      +      "type": "string"
      +    },
      +    "dayLord": {
      +      "type": "string"
      +    },
      +    "focus": {
      +      "enum": [
      +        "general",
      +        "finance"
      +      ],
      +      "type": "string"
      +    },
      +    "houseThemes": {
      +      "additionalProperties": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "type": "object"
      +    },
      +    "lagnaSignLord": {
      +      "type": "string"
      +    },
      +    "lagnaStarLord": {
      +      "type": "string"
      +    },
      +    "lagnaSubSublord": {
      +      "type": "string"
      +    },
      +    "lagnaSublord": {
      +      "type": "string"
      +    },
      +    "location": {
      +      "properties": {
      +        "latitude": {
      +          "type": "number"
      +        },
      +        "longitude": {
      +          "type": "number"
      +        },
      +        "timezone": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "latitude",
      +        "longitude",
      +        "timezone"
      +      ],
      +      "type": "object"
      +    },
      +    "moonSignLord": {
      +      "type": "string"
      +    },
      +    "moonStarLord": {
      +      "type": "string"
      +    },
      +    "moonSubSublord": {
      +      "type": "string"
      +    },
      +    "moonSublord": {
      +      "type": "string"
      +    },
      +    "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"
      +    }
      +  },
      +  "required": [
      +    "datetime",
      +    "location",
      +    "dayLord",
      +    "moonSignLord",
      +    "moonStarLord",
      +    "moonSublord",
      +    "moonSubSublord",
      +    "lagnaSignLord",
      +    "lagnaStarLord",
      +    "lagnaSublord",
      +    "lagnaSubSublord",
      +    "rulingPlanets"
      +  ],
      +  "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: +[
      +  {
      +    "latitude": 28.6139,
      +    "longitude": 77.209
      +  }
      +]
    • 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
    • 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"
      +}
  7. 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."
  8. 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"
      +}
  9. Changed2 schema fields 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"
      +  }
      +]
    • changedInput schema / properties / timezone / description
      Previous value: -"Timezone: decimal hours from UTC OR IANA name (e.g. \"Asia/Kolkata\"). IANA resolved to the DST-correct offset based on birthDate or datetime. Defaults to 5.5 (IST)."New value: +"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC. IANA resolved to the DST-correct offset based on birthDate or datetime. Defaults to 5.5."
  10. First observed

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 safety is covered. The description adds useful behavioral detail about what the significators branch returns and why it matters, but says nothing about lat/long behavior for the ruling-planets-only case, the polar-latitude 400 error, or default-time handling — all of which are covered only in the schema.

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?

Two tight sentences with the core purpose front-loaded and the optional branch second. The clause 'which is essential for KP prediction' is mild persuasion rather than operational information, but it is brief enough not to harm the structure.

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?

With an output schema present, the description needn't enumerate return values, and it covers the main optional mode. For a 10-parameter tool the description is adequate, though it could hint that latitude/longitude are still required even when no birth data is supplied.

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 baseline is 3. The description reinforces the birthDate/birthTime pairing semantics, but adds nothing beyond the schema for datetime, timezone, nodeType, focus, or lang, which are all richly documented in the schema itself.

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 and resource: 'Calculate the 5 ruling planets at any moment using Krishnamurti Paddhati horary astrology,' and then enumerates the returned components (Day Lord, Moon/Lagna sign-star-sub lord). This distinguishes it from siblings such as kp_ruling_planets_interval and kp_horary without the agent needing to open the schema.

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 clearly states the condition for the optional branch: 'Optionally provide birth data (birthDate, birthTime) to include significators,' and justifies why ('essential for KP prediction'). However, it never names an alternative tool or says when to prefer kp_horary, kp_chart, or the interval variant instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources