Skip to main content
Glama

AstroLogics

Shani Sade Sati check

check_sade_sati
Read-onlyIdempotent

Check whether Shani Sade Sati or Dhaiya (Saturn's transit over the natal Moon) is running for a person, which phase, its dates, and the full list of Sade Sati and Dhaiya windows across about 30 years around now. Based on the Moon sign; birth time is needed only when the Moon changed sign on the birth date.

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>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "check_sade_sati"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD.
timeNoLocal birth time, HH:MM. Optional.
languageNoSet to "hi" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.
latitudeYesBirth latitude in decimal degrees.
longitudeYesBirth longitude in decimal degrees.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.",
      +  "enum": [
      +    "en",
      +    "hi"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare a safe, read-only, idempotent, closed-world operation, so the safety bar is covered. Beyond that, the description discloses the calculation basis (natal Moon), the conditional dependency on birth time, and the scope of the returned window (~30 years around now), which is real context an agent would otherwise have to guess.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Everything arrives in one front-loaded sentence: what is checked, how it is computed, what is returned, and the optional-input caveat. There is no filler, restatement of the title, or trailing boilerplate.

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?

There is no output schema, so the description must describe the return, and it does: running status, phase, dates, and the full window list. Combined with annotations covering the safety profile and full schema coverage on the inputs, nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description earns a bump by explaining that time is optional in a non-obvious way: it matters only for the sign-boundary case, and it clarifies that the moment-derived inputs feed a Moon-sign computation rather than a full chart.

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 a specific verb and subject (check whether Shani Sade Sati or Dhaiya is running), defines the astronomical basis (Saturn's transit over the natal Moon), and enumerates what is returned: phase, dates, and a ~30-year list of windows. That is enough to distinguish it from sibling dasha and dosha tools 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?

It states the operative input, 'Based on the Moon sign,' and gives an explicit condition for the optional birth time: needed only when the Moon changed sign on the birth date. It does not name an alternative or a when-not-to-use case, which keeps it 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