Skip to main content
Glama

Moon Dasha Vedic Astrology

Transits of Jupiter, Saturn, Rahu and Ketu

transits
Read-onlyIdempotent

Follow Jupiter, Saturn, Rahu and Ketu against a Vedic birth chart with Moon Dasha's calculations, over a window (two years from today by default): each sign stay with its dates, the house it transits from the Ascendant and from the Moon, its dignity, its Ashtakavarga points and Moon Dasha's rating of the stay (its own reading, not a probability), the classical good houses from the Moon, the houses it aspects, its stations, the exact days it passes natal planets, and any dasha of that planet the person runs meanwhile; and the transit chart, the nine planets now beside the natal ones, from the Ascendant and from the Moon. Sade Sati's phases and dates come from sade_sati. Needs the birth date, the local birth time and the birthplace (a place_id from find_place). Word transits as tendencies; never predict death, illness, accidents, a relative's death, 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": "transits"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD.
fromNoThe first day of the window, YYYY-MM-DD. Default today, when the transit chart shows the planets now; on a given day it shows them at noon.
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.
monthsNoHow many months the window covers, 1 to 120. Default 24.
ayanamsaNoDefault Lahiri. Krishnamurti is the KP ayanamsa.
place_idYesThe place_id find_place returned for the birthplace.
time_is_approximateNoSet when the birth time is a guess: the answer then says whether the Ascendant or the Moon would be in another sign an hour either side, which shifts the houses counted from it.

Output Schema

NameRequiredDescriptionDefault
toYes
fromYes
birthYes
chartYes
notesYes
staysYes
settingsYes
moon_signYes
chart_linkYes
approximateYes
ascendant_signYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond that: the default window is two years, the Moon Dasha rating is an interpretive reading rather than a probability, and the output is framed as tendencies with explicit forbidden prediction topics. That interpretive and policy context is not available from 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.

Conciseness3/5

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

Purpose is front-loaded, but the core sentence is a long enumeration that runs on through many clauses joined by 'and', and the trailing 'and the transit chart, the nine planets now beside the natal ones' is awkwardly spliced in. The final two sentences about requirements and content policy are tight and earn their place, but the middle enumeration could be structured as a list.

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?

An output schema exists, so return values need no explanation, and the description still covers prerequisites, window defaults, ayanamsa default, and the interpretive-caution policy. Given an 8-parameter tool with three required inputs, the only thing left implicit is how this differs from non-transit chart tools like birth_chart. That is a minor omission against an otherwise complete definition.

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 parameter docs are already detailed (time explains the approximate-birth-time fallback, from explains noon behavior, ayanamsa names the KP option). The description restates the two-year default and the place_id provenance, which is modest added meaning rather than new information. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 names the specific planets tracked (Jupiter, Saturn, Rahu, Ketu), the reference frame (a Vedic birth chart with Moon Dasha), the window, and enumerates what each result contains (sign stays with dates, houses from Ascendant and Moon, dignity, Ashtakavarga points, aspects, stations). It also explicitly separates Sade Sati out to the sade_sati sibling, so an agent can distinguish it from that tool without opening a 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?

Usage context is explicit: it needs a birth date, local birth time, and a place_id obtained from find_place, and it routes Sade Sati questions to sade_sati. It also sets a content boundary (frame as tendencies; never predict death, illness, accidents, markets, elections, court cases). It stops short of saying when to prefer this over birth_chart or planetary_positions, which is the only gap.

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