Skip to main content
Glama

Supastro

Find the eclipses of a year for a birth chart

get_eclipses
Read-onlyIdempotent

Calculates the solar and lunar eclipses of a year against a birth chart: each eclipse's date and type, the sidereal sign and nakshatra it falls in, the house it falls in counted from the rising sign and from the birth Moon, and the traditional reading of that count from the Moon sign. For a place it also says whether the eclipse is visible there, the local times of each contact and the Sutak window. Use it when someone asks about upcoming eclipses (grahan), whether one is visible where they live, its Sutak times, or where an eclipse falls in their chart.

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_eclipses"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoOptional. The calendar year, from last year to ten years ahead. Defaults to this year.
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".
viewing_placeNoOptional. City and country to check visibility and local times for. Defaults to the birth place.
viewing_latitudeNoOptional. Latitude of the viewing place. Only together with viewing_longitude.
viewing_longitudeNoOptional. Longitude of the viewing place. Only together with viewing_latitude.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds substantial behavioral context: the calculation is chart-relative, visibility/local-time output depends on a place, and results include a traditional interpretation layer. It does not cover failure modes (e.g., what happens with an invalid birthplace or a year outside the supported range), which keeps it off a 5.

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?

Two sentences, front-loaded with the core action and ending with routing triggers. The first sentence is long and clause-heavy, but nearly every clause names a distinct returned field rather than padding, so the density is functional rather than wasteful.

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?

Nine parameters, no output schema, and a domain-specific calculation: the description compensates fully by describing the entire return surface (dates, types, sign/nakshatra, dual house counts, interpretation, visibility, contact times, Sutak). An agent can decide to call it and set user expectations without additional information.

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 coverage is 100%, so 3 is the baseline, but the description earns an extra point by linking parameters to outputs rather than restating them: 'For a place it also says whether the eclipse is visible there, the local times of each contact and the Sutak window' explains what viewing_place/viewing_latitude/viewing_longitude actually unlock, which the schema alone does not convey.

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 opens with a specific verb and resource: 'Calculates the solar and lunar eclipses of a year against a birth chart.' It then enumerates exactly what each result contains (date, type, sidereal sign, nakshatra, house from rising sign and from Moon, traditional reading, visibility, contact times, Sutak window), which distinguishes it from chart-wide siblings like cast_birth_chart or get_panchang without needing their schemas.

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 final sentence gives concrete user intents that should route here: upcoming eclipses (grahan), local visibility, Sutak times, or eclipse placement in a chart, including the Hindi term users may actually type. It stops short of naming an alternative tool or stating when not to use it, so it is clear context rather than 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