Asterwise

Ashtottari Dasha

asterwise_get_ashtottari_dasha

Read-onlyIdempotent

Computes the Ashtottari Dasha tree (108-year cycle) with configurable depth, levels 1–5. The timeline continues into the next cycle until it reaches at least age 120 (usually 9–11 mahadashas); periods are under data.periods.root with DD/MM/YYYY dates.

WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — chart context before choosing between Ashtottari and Vimshottari. AFTER: asterwise_get_dasha — optional Vimshottari comparison.

INPUT CONTRACT: levels: same as asterwise_get_dasha (1–5, default 2), enforced locally before the API call. Periods use data.periods.root[], not data.periods[]. Dates in periods are DD/MM/YYYY.

DO NOT CONFUSE WITH: asterwise_get_dasha — standard 120-year Vimshottari with data.periods[], not Ashtottari or data.periods.root[]. asterwise_get_yogini_dasha — 36-year Yogini cycle with yogini names on each row.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-ashtottari-dasha/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`birth`	Yes	Birth data for a single person.
`levels`	No	Depth of the Ashtottari tree, 1-5: 1 = Mahadasha only, 2 adds Antardasha (default), 3 Pratyantar, 4 Sookshma, 5 Prana.
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026

changedInput schema / properties / levels / default
```
Previous value: -3New value: +2
```

changedInput schema / properties / levels / description

Previous value: -"Depth of the dasha tree: 1 returns major periods only, each extra level adds the next sub-period layer."New value: +"Depth of the Ashtottari tree, 1-5: 1 = Mahadasha only, 2 adds Antardasha (default), 3 Pratyantar, 4 Sookshma, 5 Prana."

Changed2 schema fields changedSep 5, 2026

addedInput schema / properties / levels / description

Added value: +"Depth of the dasha tree: 1 returns major periods only, each extra level adds the next sub-period layer."

addedInput schema / properties / response_format / description

Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."

Changed8 schema fields changedSep 4, 2026

changedInput schema / properties / birth / properties / date / description

Previous value: -"Birth date in YYYY-MM-DD format. Example: '1985-11-12'"New value: +"Birth date YYYY-MM-DD."

changedInput schema / properties / birth / properties / lat / description

Previous value: -"Birth latitude in decimal degrees. North positive, south negative. Example: 19.0760 for Mumbai, -33.8688 for Sydney"New value: +"Latitude in decimal degrees, north positive (Mumbai 19.076)."

changedInput schema / properties / birth / properties / lon / description

Previous value: -"Birth longitude in decimal degrees. East positive, west negative. Example: 72.8777 for Mumbai, -74.0060 for New York"New value: +"Longitude in decimal degrees, east positive (Mumbai 72.8777)."

changedInput schema / properties / birth / properties / person_name / description

Previous value: -"Name of the person for this chart. Example: 'Arjun Mehta'"New value: +"Person's name, used in labels only."

changedInput schema / properties / birth / properties / time / description

Previous value: -"Birth time in HH:MM 24-hour format. Example: '06:45'. Omit entirely if the birth time is unknown: a sunrise chart is used and birth_time_provided returns false. Do not pass '00:00' for an unknown time, it is treated as a real midnight birth and returns a confidently wrong ascendant."New value: +"Birth time HH:MM (24h), e.g. '06:45'. Omit if unknown (a sunrise chart is used and birth_time_provided=false); never pass '00:00' for unknown."

changedInput schema / properties / birth / properties / timezone / description

Previous value: -"IANA timezone for the birth location. Examples: 'Asia/Kolkata' (India), 'America/New_York' (New York), 'Europe/London' (London), 'Asia/Tokyo' (Japan), 'America/Los_Angeles' (Los Angeles), 'Europe/Paris' (Paris), 'Asia/Dubai' (Dubai), 'Asia/Singapore' (Singapore), 'America/Chicago' (Chicago), 'Australia/Sydney' (Sydney). Default: Asia/Kolkata"New value: +"IANA timezone of the birth place, e.g. 'Asia/Kolkata', 'America/New_York', 'Europe/London'. Default: Asia/Kolkata"

addedInput schema / properties / response_format / default
```
Added value: +"markdown"
```

changedInput schema / required

Previous value: -[
-  "birth",
-  "response_format"
-]New value: +[
+  "birth"
+]

Changed6 schema fields changedJul 25, 2026

addedInput schema / properties / birth / properties / time / anyOf

Added value: +[
+  {
+    "pattern": "^\\d{2}:\\d{2}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / birth / properties / time / default
```
Added value: +null
```

changedInput schema / properties / birth / properties / time / description

Previous value: -"Birth time in HH:MM format (24-hour). Example: '06:45'. Use '00:00' if unknown."New value: +"Birth time in HH:MM 24-hour format. Example: '06:45'. Omit entirely if the birth time is unknown: a sunrise chart is used and birth_time_provided returns false. Do not pass '00:00' for an unknown time, it is treated as a real midnight birth and returns a confidently wrong ascendant."

removedInput schema / properties / birth / properties / time / pattern
```
Removed value: -"^\\d{2}:\\d{2}$"
```
removedInput schema / properties / birth / properties / time / type
```
Removed value: -"string"
```

changedInput schema / properties / birth / required

Previous value: -[
-  "date",
-  "time",
-  "lat",
-  "lon"
-]New value: +[
+  "date",
+  "lat",
+  "lon"
+]

First observedApr 22, 2026

TDQS

Score is being calculated.

All Asterwise tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?