Vedic Astrology and Kundli MCP Server by RoxyAPI

Get all Sookshma dashas for a Mahadasha, Antardasha and Pratyantardasha

post_vedic_astrology_dasha_sub_mahadasha_antardasha_pratyantardasha

Read-only

Sookshma dasha API. Returns the 9 Sookshma periods inside a chosen Pratyantardasha, the fourth and finest level of the Vimshottari dasha hierarchy. Completes a full vimshottari drill down from the 120-year cycle to day level timing, typically 3 to 30 days per period. Built for dasha drill down tables, current DBA readouts, and precise event timing in Vedic astrology software.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes	Birth 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).
`lang`	No	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.	en
`time`	Yes	Birth 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.
`focus`	No	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".	general
`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 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
`latitude`	Yes	Birth 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.
`nodeType`	No	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".	mean
`timezone`	No	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.
`longitude`	Yes	Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.
`mahadasha`	Yes	Mahadasha planet name, case-insensitive. Valid: Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury.
`antardasha`	Yes	Antardasha (bhukti) planet name inside that Mahadasha, case-insensitive.
`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.
`significators`	No	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.
`pratyantardasha`	Yes	Pratyantardasha (antara) planet name inside that Antardasha, case-insensitive.

TDQS

A4/5.0

Behavior4/5

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

Annotations already mark the tool read-only and non-destructive. The description adds meaningful behavioral context that is not in the annotations: it returns exactly 9 Sookshma periods, each typically 3 to 30 days long, at the fourth/finest level of the hierarchy. It does not contradict the annotations.

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 appropriately sized and well organized: the precise result is stated first, then the hierarchy level and granularity, then the expected use cases. The phrase 'Sookshma dasha API' is slightly redundant with the name, but every other sentence contributes useful signal and the whole remains concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only calculation tool with an extensively described 15-parameter schema, this description is complete enough to select and invoke it: it states the exact output count, the period length, the hierarchy level, the input prerequisite, and realistic domains such as drill-down tables and event timing. The absence of an output schema is not serious because the description already specifies the return granularity and scope.

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% and every parameter already has a detailed description, so the description's parameter contribution is minimal. The text adds general context about the returned periods but does not add specific parameter meaning beyond what the schema already provides; baseline 3 is therefore appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is specific: it returns the 9 Sookshma periods inside a chosen Pratyantardasha and situates that resource in the Vimshottari hierarchy. It clearly states the resource and the granularity of the result, though it does not distinguish itself from the similarly named sibling tool ..._sookshma, so it misses the explicit sibling differentiation needed for a 5.

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 usage context: it is built for dasha drill-down tables, current dasha readouts, and precise event timing, and it makes plain that the caller supplies a Mahadasha, Antardasha, and Pratyantardasha. It does not name alternative sibling tools or add when-not-to-use exclusions, so no explicit comparison is offered.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation3/5

Many tools have overlapping concepts (multiple dasha levels, monthly variants, aspects, transit), but detailed descriptions clarify each one's distinct purpose. Still, a few pairs like planetary_positions vs birth_chart or aspects_monthly vs aspects_lunar could confuse an agent initially.

Naming Consistency5/5

All tools follow a strict get_vedic_astrology_* or post_vedic_astrology_* prefix with snake_case resource names. The pattern is predictable and uniformly applied, including the hierarchical dasha drill-downs, making it easy to infer tool families.

Tool Count1/5

With 50 tools, the server is extremely heavy. Many are monthly, interval, or sub-level variants that could be parameterized or consolidated, making the set feel bloated and difficult to navigate for an agent.

Completeness5/5

The tool set covers nearly the entire Vedic astrology domain: reference data (nakshatras, rashis, yoga glossary), core charts (birth, navamsa, divisional), dasha hierarchy, transits, compatibility, doshas, panchang, KP system, and advanced calculations like Shadbala and Ashtakavarga. No significant gaps are apparent.

Resources

Need Help?