Skip to main content
Glama

Moon Dasha Vedic Astrology

Dasha periods

dasha_periods
Read-onlyIdempotent

Calculate Vedic dasha periods with Moon Dasha in any of seven systems: Vimshottari (default), Yogini, Ashtottari, Chara (K. N. Rao), Kaal Chakra, Narayana and Sudarshan Chakra. Returns the Mahadashas with their dates to the 120th year of life, across cycles (Sudarshan Chakra: the 12 years of the running cycle), the Mahadasha, Antardasha and Pratyantardasha running on a given day (default today; Sudarshan Chakra: the year and its month), and the running Mahadasha's Antardashas, plus a link to the dashas on moondasha.com. Needs the birth date, the local birth time and the birthplace (a place_id from find_place). If the person does not know the birth time, ask for a best guess and set time_is_approximate. The figures are Moon Dasha's calculations. Interpret them with care and never predict death, illness, a child's sex, markets, elections or court cases.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>",
      "time": "<time>",
      "place_id": "<place_id>"
    },
    "name": "dasha_periods"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD.
nodeNoRahu and Ketu by the mean node (default) or the true node.
timeYesLocal clock time at the birthplace, 24-hour HH:MM or HH:MM:SS. Required: if the person does not know it, ask for their best guess and set time_is_approximate.
as_ofNoThe day whose running periods to show, YYYY-MM-DD, from the birth date to the 120th year of life. Default today.
systemNoThe dasha system: vimshottari (default), yogini, ashtottari, chara (K. N. Rao), kaal_chakra, narayana or sudarshan_chakra. Use the one the person asks for.
ayanamsaNoDefault Lahiri. Krishnamurti is the KP ayanamsa.
place_idYesThe place_id find_place returned for the birthplace.
dasha_yearNoThe year the periods count in: true_sidereal (default), mean_sidereal, true_tropical, mean_tropical or savana (360 days). Set it only when the person asks for one.
time_is_approximateNoSet when the birth time is a guess: the answer then shows the running periods an hour either side and how far the dates move.

Output Schema

NameRequiredDescriptionDefault
as_ofYes
birthYes
cycleYesSudarshan Chakra's 12-year cycle of the listed years, 0 for ages 0 to 11; null for the other systems.
systemYes
runningYes
calendarYes
settingsYes
chart_linkYes
mahadashasYes
antardashasYes
approximateYes
system_nameYes
as_of_momentYesThe moment the running periods are read at: noon of as_of on the birth's clock, or the birth itself on a birth day after noon.
ascendant_signYes
moon_nakshatraYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: what is returned (Mahadashas to the 120th year, current Mahadasha/Antardasha/Pratyantardasha, the running Mahadasha's Antardashas, an external link), how results degrade when time_is_approximate (shows periods an hour either side and how far dates move), and whose calculations these are. That is helpful but mostly output description rather than operational behavior.

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?

Front-loaded with the systems list, then returns, then inputs, then safety caveat — a sensible ordering with no filler sentences. It is a dense single block that repeats some schema content, which keeps it just short of a 5.

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 nine parameters, four enums and an existing output schema, the description covers the essentials an agent needs to call it correctly, including cross-tool guidance to find_place for place_id. The only slack is that it restates schema-level defaults instead of spending those words on anything not already structured.

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 schema already documents date, time, as_of, system, ayanamsa, place_id, dasha_year and time_is_approximate in detail. The description largely restates the same facts (required triplet, today default, approximate-time handling) rather than adding new semantics. Baseline 3 applies because the schema carries the parameter burden.

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?

Opens with a specific verb+resource ("Calculate Vedic dasha periods") and immediately enumerates all seven supported systems with their defaults, so an agent knows exactly what computation this tool performs and which variants it supports. The scope is narrow and unambiguous versus observational siblings such as planetary_positions or panchang.

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?

Gives concrete invocation conditions: the required birth date, local birth time and place_id from find_place, plus an explicit fallback ("If the person does not know the birth time, ask for a best guess and set time_is_approximate"). It also says to use the system the person asks for and to set dasha_year only when requested. It never names an alternative sibling tool to use instead, so it falls short of a 5.

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