Skip to main content
Glama

Supastro

Check Sade Sati status

check_sade_sati
Read-onlyIdempotent

Checks whether Saturn's Sade Sati is running for a birth: active or not, which of its three phases, Saturn's current sign and its position counted from the birth Moon sign, the dates of the current stay and of the whole Sade Sati, or when the next one begins. Also reports Saturn in the 4th or 8th sign from the Moon. Use it when someone asks whether they are in Sade Sati or when it starts or ends. Returns status and dates only, with no interpretation.

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": "check_sade_sati"
  }
}

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and side-effect questions are answered structurally. The description adds meaningful scope beyond that: 'Returns status and dates only, with no interpretation,' which tells the agent not to expect a narrative reading. It does not mention error behavior for unresolvable birth places, but that is a minor omission given the annotation coverage.

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?

Content is front-loaded: what it checks, what it returns, when to use it, and the no-interpretation boundary, in that order. Every clause carries information. The first sentence is long and comma-chained, which slightly hurts scannability against an otherwise tight structure.

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?

With no output schema, the description correctly spends its words enumerating return content (status, phase, signs, dates, next start), which is exactly what an agent needs to match against a user request. Required birth inputs are signaled by 'for a birth' and fully specified in the schema. What is missing is only the relative positioning versus the lifetime sibling, which matters for a catalog of this size.

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 descriptions are unusually thorough (date-order disambiguation, AM/PM handling, coordinate pairing rules). The description adds nothing about parameters beyond the phrase 'for a birth,' so it neither compensates nor needs to; baseline 3 applies when the schema carries the semantics.

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 names a specific verb and resource (checks whether Saturn's Sade Sati is running for a birth) and enumerates the exact outputs: active/not, which of three phases, Saturn's sign and position from the Moon, stay dates, and 4th/8th-sign status. It is far more specific than the title alone. It stops short of naming or contrasting the obvious sibling get_sade_sati_lifetime, so an agent must infer the split between a current-status check and a lifetime schedule.

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?

Explicit trigger conditions are given: 'Use it when someone asks whether they are in Sade Sati or when it starts or ends.' That maps cleanly onto real user questions. There are no exclusions or named alternatives, however, so a question like 'show me all my Sade Sati periods across life' is not explicitly routed elsewhere.

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