Skip to main content
Glama

Supastro

List every Sade Sati in a lifetime

get_sade_sati_lifetime
Read-onlyIdempotent

Calculates every Sade Sati across 90 years of a life, with dates: each Sade Sati's start and end, its rising, peak and setting phases with every stay of Saturn (retrograde re-entries included), and each Kantaka Shani (Saturn in the 4th from the Moon) and Ashtama Shani (8th from the Moon). It also gives the Sarvashtakavarga points of the signs Saturn crosses, which the classical scale reads as lighter or heavier. Use it when someone asks when their Sade Sati was, is or will be, how many they will have, or for the dates of each phase.

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": {
      "birth_date": "<birth_date>",
      "birth_time": "<birth_time>",
      "birth_place": "<birth_place>"
    },
    "name": "get_sade_sati_lifetime"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeNoOptional. Latitude of the birth place in decimal degrees, north positive. Give it only together with longitude, when the user supplied coordinates or the place could not be found by name.
longitudeNoOptional. Longitude of the birth place in decimal degrees, east positive. Give it only together with latitude.
birth_dateYesDate of birth as YYYY-MM-DD, for example 1990-01-15 for 15 January 1990. People write dates in different orders: day first in India and most countries, month first in the United States. Convert what the person wrote to YYYY-MM-DD yourself. If an all-number date could be read two ways, such as 05-06-1990, ask which number is the day before calling; never assume.
birth_timeYesLocal clock time of birth at the birth place, 24-hour HH:MM, for example 10:30, or 16:26 for 4:26 PM. If the person gave an hour from 1 to 12 without AM or PM, ask which before calling. Ask the user if the time is unknown; do not guess it.
birth_placeYesCity and country of birth, for example "Mumbai, India".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world calculation. Beyond that, the description adds meaningful output behavior: the 90-year horizon, start/end dates, rising/peak/setting phases, retrograde re-entries, Kantaka and Ashtama Shani, and Sarvashtakavarga points.

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 definition is front-loaded with what the tool calculates and follows with a clear usage sentence. It is dense but appropriate for a complex astrological calculation, with little obvious waste.

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?

For a complex calculation without an output schema, the description explains the returned content well enough to know what to expect. The input schema fully documents the required birth details, so the definition is largely complete.

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 birth date, birth time, birth place and optional coordinates in detail. The description does not add any parameter-specific meaning beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource: it calculates every Sade Sati across a 90-year lifetime, including phase dates and related Saturn periods. The scope is clear enough to separate it from a simple current-status check, but it does not explicitly name or contrast with the sibling check_sade_sati.

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?

It gives clear triggering questions: when a Sade Sati was, is or will be, how many will occur, or the dates of each phase. It does not state when not to use it or name an alternative for simpler status checks, so it stops short of full routing guidance.

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