Skip to main content
Glama

Moon Dasha Vedic Astrology

Sade Sati and Saturn cycles

sade_sati
Read-onlyIdempotent

Find Sade Sati for a birth with Moon Dasha's calculations: whether it is running, its three phases (Rising, Peak, Setting) and their exact dates, and when the next one comes; also Kantaka Shani and Ashtama Shani (Saturn in the 4th and 8th signs from the Moon, called Dhaiya) and the Saturn Return, over the person's life. Counted by sign from the natal Moon sign. Needs the birth date, the local birth time and the birthplace (a place_id from find_place). Describe these periods as stretches of pressure and responsibility, never misfortune, and suggest no remedies; never predict death, illness, accidents, a relative's death, markets 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": "sade_sati"
  }
}

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 that decides which cycles are past, running or upcoming, YYYY-MM-DD. Default today.
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: when the Moon changes sign within an hour either side, the answer also gives that sign's Sade Sati.

Output Schema

NameRequiredDescriptionDefault
as_ofYes
birthYes
notesYes
cyclesYes
throughYes
settingsYes
moon_signYes
chart_linkYes
approximateYes
saturn_sign_at_birthYes
counted_from_the_moonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With readOnlyHint, idempotentHint, and openWorldHint=false already supplied, the description adds useful behavioral context: calculations are counted by sign from the natal Moon sign, phases have exact dates, and results span the person's life. It also gives strong output-content guardrails about framing periods as pressure and responsibility, avoiding misfortune language, remedies, and predictions of death, illness, accidents, or markets.

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 front-loaded with the core computation and then adds important constraints. It is dense but well organized; the long first sentence and the output-framing sentence both earn their place, though the description could be slightly tighter.

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 complex, multi-parameter astrological calculation tool with an output schema, the description covers purpose, required inputs, included Saturn cycles, counting method, and output-content constraints. Return values are appropriately left to the output schema, and no essential calling information appears to be missing.

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 explains date, time, place_id, as_of, ayanamsa, node, and time_is_approximate. The description reinforces the required birth inputs and the find_place dependency, but does not add substantive meaning beyond the schema for the remaining parameters.

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 uses a specific verb and resource: 'Find Sade Sati for a birth,' and enumerates the exact outputs including running status, three phases with dates, next occurrence, Kantaka Shani, Ashtama Shani, and Saturn Return. This is sufficiently distinct from siblings such as dasha_periods or transits, and names find_place as the source of place_id.

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 establishes the context clearly ('for a birth,' 'over the person's life') and states the required inputs, including that place_id comes from find_place. It does not explicitly compare this tool with sibling alternatives like transits or dasha_periods, so it falls short of a full when-to-use/when-not-to-use guideline.

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