Skip to main content
Glama

Vedic Astrology and Kundli MCP Server by RoxyAPI

Get all 9 Mahadasha periods (120-year cycle)

post_vedic_astrology_dasha_major
Read-only

Returns the complete Vimshottari dasha cycle from birth, all 9 Mahadasha periods across the full 120 year span. Each period carries its ruling graha, exact start and end dates, and the houses it signifies, with the birth dasha balance and Moon nakshatra that anchor the sequence. This is the top level timeline a Vedic astrology report opens with, and the entry point for drilling into Antardasha and finer sub periods.

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).
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
timeYesBirth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.
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 used to place the birth Moon in its nakshatra, which sets every dasha start and end date. "lahiri" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. "kp-newcomb" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. "kp-old" uses the Krishnamurti original table from KP Reader-1. "raman" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.lahiri
latitudeYesBirth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.
nodeTypeNoLunar node type for Rahu and Ketu, used ONLY when "significators" is true. Dasha dates themselves come from the Moon and never move with this field. "mean" uses the smooth mean node (traditional default). "true" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. 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 to the offset in force at the given date and time. Defaults to 5.5.
longitudeYesBirth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.
ayanamsaValueNoCustom 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.
significatorsNoSet true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.

Output Schema

NameRequiredDescriptionDefault
focusNo
ayanamsaYes
mahadashasYes
totalYearsYes
houseThemesNo
ayanamsaTypeYes
moonLongitudeYes
moonNakshatraYes
nakshatraLordYes
nakshatraNameYes
birthDashaBalanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / significators / description
      Previous value: -"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above."New value: +"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400."
  2. Changed1 schema field changed
    • changedInput schema / properties / timezone / description
      Previous value: -"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5."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."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "ayanamsa": {
      +      "type": "number"
      +    },
      +    "ayanamsaType": {
      +      "enum": [
      +        "kp-newcomb",
      +        "kp-old",
      +        "lahiri",
      +        "raman",
      +        "custom"
      +      ],
      +      "type": "string"
      +    },
      +    "birthDashaBalance": {
      +      "properties": {
      +        "days": {
      +          "type": "number"
      +        },
      +        "months": {
      +          "type": "number"
      +        },
      +        "totalDays": {
      +          "type": "number"
      +        },
      +        "years": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "years",
      +        "months",
      +        "days",
      +        "totalDays"
      +      ],
      +      "type": "object"
      +    },
      +    "focus": {
      +      "enum": [
      +        "general",
      +        "finance"
      +      ],
      +      "type": "string"
      +    },
      +    "houseThemes": {
      +      "additionalProperties": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "type": "object"
      +    },
      +    "mahadashas": {
      +      "items": {
      +        "properties": {
      +          "durationYears": {
      +            "type": "number"
      +          },
      +          "endDate": {
      +            "type": "string"
      +          },
      +          "interpretation": {
      +            "type": "string"
      +          },
      +          "nominalStartDate": {
      +            "type": "string"
      +          },
      +          "planet": {
      +            "enum": [
      +              "Ketu",
      +              "Venus",
      +              "Sun",
      +              "Moon",
      +              "Mars",
      +              "Rahu",
      +              "Jupiter",
      +              "Saturn",
      +              "Mercury"
      +            ],
      +            "type": "string"
      +          },
      +          "significators": {
      +            "properties": {
      +              "house": {
      +                "maximum": 12,
      +                "minimum": 1,
      +                "type": "integer"
      +              },
      +              "signifiedHouses": {
      +                "items": {
      +                  "maximum": 12,
      +                  "minimum": 1,
      +                  "type": "integer"
      +                },
      +                "type": "array"
      +              },
      +              "signifies": {
      +                "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"
      +              },
      +              "starLord": {
      +                "type": "string"
      +              },
      +              "strength": {
      +                "properties": {
      +                  "grade": {
      +                    "enum": [
      +                      "A",
      +                      "B",
      +                      "C",
      +                      "D"
      +                    ],
      +                    "type": "string"
      +                  },
      +                  "label": {
      +                    "enum": [
      +                      "very-strong",
      +                      "strong",
      +                      "moderate",
      +                      "weak"
      +                    ],
      +                    "type": "string"
      +                  },
      +                  "score": {
      +                    "maximum": 100,
      +                    "minimum": 0,
      +                    "type": "number"
      +                  }
      +                },
      +                "required": [
      +                  "score",
      +                  "grade",
      +                  "label"
      +                ],
      +                "type": "object"
      +              },
      +              "strongHouses": {
      +                "items": {
      +                  "maximum": 12,
      +                  "minimum": 1,
      +                  "type": "integer"
      +                },
      +                "type": "array"
      +              },
      +              "subLord": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "house",
      +              "starLord",
      +              "signifies",
      +              "signifiedHouses",
      +              "strongHouses",
      +              "strength"
      +            ],
      +            "type": "object"
      +          },
      +          "startDate": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "planet",
      +          "startDate",
      +          "endDate",
      +          "durationYears"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "moonLongitude": {
      +      "type": "number"
      +    },
      +    "moonNakshatra": {
      +      "maximum": 27,
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    "nakshatraLord": {
      +      "enum": [
      +        "Ketu",
      +        "Venus",
      +        "Sun",
      +        "Moon",
      +        "Mars",
      +        "Rahu",
      +        "Jupiter",
      +        "Saturn",
      +        "Mercury"
      +      ],
      +      "type": "string"
      +    },
      +    "nakshatraName": {
      +      "type": "string"
      +    },
      +    "totalYears": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "moonNakshatra",
      +    "nakshatraName",
      +    "nakshatraLord",
      +    "moonLongitude",
      +    "ayanamsa",
      +    "ayanamsaType",
      +    "birthDashaBalance",
      +    "mahadashas",
      +    "totalYears"
      +  ],
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / timezone / description
      Previous value: -"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5."New value: +"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5."
  5. 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"
      +]
  6. Changed2 schema fields changed
    • 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."
  7. Changed2 schema fields changed
    • changedInput schema / properties / ayanamsa / description
      Previous value: -"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses."New value: +"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses."
    • changedInput schema / properties / ayanamsa / enum
      Previous value: -[
      -  "kp-newcomb",
      -  "kp-old",
      -  "lahiri",
      -  "custom"
      -]New value: +[
      +  "kp-newcomb",
      +  "kp-old",
      +  "lahiri",
      +  "raman",
      +  "custom"
      +]
  8. Changed3 schema fields changed
    • changedInput schema / properties / ayanamsa / description
      Previous value: -"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses."New value: +"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses."
    • changedInput schema / properties / ayanamsa / enum
      Previous value: -[
      -  "kp-newcomb",
      -  "kp-old",
      -  "lahiri"
      -]New value: +[
      +  "kp-newcomb",
      +  "kp-old",
      +  "lahiri",
      +  "custom"
      +]
    • addedInput schema / properties / ayanamsaValue
      Added value: +{
      +  "description": "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.",
      +  "example": 24,
      +  "type": "number"
      +}
  9. Changed1 schema field 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"
      +}
  10. Changed2 schema fields changed
    • addedInput schema / properties / nodeType
      Added value: +{
      +  "default": "mean",
      +  "description": "Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".",
      +  "enum": [
      +    "mean",
      +    "true"
      +  ],
      +  "example": "mean",
      +  "type": "string"
      +}
    • addedInput schema / properties / significators
      Added value: +{
      +  "default": false,
      +  "description": "Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.",
      +  "example": false,
      +  "type": "boolean"
      +}
  11. Changed1 schema field changed
    • addedInput schema / properties / ayanamsa
      Added value: +{
      +  "default": "lahiri",
      +  "description": "Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.",
      +  "enum": [
      +    "kp-newcomb",
      +    "kp-old",
      +    "lahiri"
      +  ],
      +  "example": "lahiri",
      +  "type": "string"
      +}
  12. 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."
  13. 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"
      +}
  14. 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 (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. \"Asia/Kolkata\", \"America/New_York\"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5 (IST)."New value: +"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5."
  15. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the description's added value is scope disclosure: the full 120-year cycle from birth, anchored to birth dasha balance and Moon nakshatra. It does not cover error behavior or the significators/polar-latitude constraint, but those are already documented 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences with no filler: what is returned, what each period contains, and where it sits in the report hierarchy. The entry-point framing is front-loaded before the drilling-down hint.

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 explain return values, and annotations carry the safety profile; what remains is purpose and placement in the tool family, both handled. A minor gap is that it doesn't surface the ayanamsa-dependence of dasha boundaries, which the schema calls out as shifting every boundary by weeks.

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% and the parameters are richly documented there (ayanamsa frames, timezone resolution, focus vocabulary, compact shape, polar latitude limit). The description adds no parameter-level guidance of its own, so the baseline 3 applies.

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?

States a specific verb and resource (returns the complete Vimshottari dasha cycle, all 9 Mahadasha periods across 120 years) and enumerates the payload: ruling graha, exact start/end dates, signified houses, birth dasha balance, Moon nakshatra. This is clearly distinguishable from the sibling sub-period and current-dasha tools without opening any 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?

Positions the tool as 'the top level timeline a Vedic astrology report opens with' and 'the entry point for drilling into Antardasha and finer sub periods', which tells the agent to start here before the sub_mahadasha siblings. It stops short of naming the alternative tools or stating when NOT to use it (e.g. for the currently running dasha, where post_vedic_astrology_dasha_current would apply).

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