Skip to main content
Glama

Supastro

Find the major transits for a birth chart

get_major_transits
Read-onlyIdempotent

Calculates one slow-planet transit against a birth chart, with exact dates: Jupiter's transit through a year, each return of Saturn to its birth position, the current and next stay of the Rahu-Ketu axis, or each Mercury retrograde in the coming 14 months. For each stay it gives the house from the rising sign and from the Moon, the planet's own Ashtakavarga points in that sign, exact contacts with birth planets, and the result under the stated classical rules. Use it when someone asks about their Saturn return, where Jupiter is transiting for them this year, the Rahu-Ketu transit, or Mercury retrograde for 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>",
      "transit": "<transit>"
    },
    "name": "get_major_transits"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoOptional, for jupiter only. The calendar year to cover, from last year to three years ahead. Defaults to this year.
transitYesWhich transit to calculate.
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

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so safety is covered. The description adds substantive context the annotations cannot: exactly what each result contains (house from rising sign and from Moon, Ashtakavarga points, exact contacts, classical-rule verdict), which matters because there is no output schema. It does not discuss failure modes such as unknown birth time or high-latitude houses.

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?

Front-loaded with purpose, then outputs, then use cases — a sensible order. There is mild redundancy: the four transit types are enumerated in sentence one and again as example questions at the end, costing some length in a two-sentence block.

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 carries the return-value burden and does so reasonably, naming the computed fields per stay. Combined with a fully described 7-parameter schema and rich annotations, an agent has enough to call it correctly; only edge-case behavior (unknown birth time, coordinate fallback outcomes) is left unstated.

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 every parameter is already documented in detail, including date-format disambiguation and lat/long pairing rules. The description adds only an implicit link between 'Jupiter's transit through a year' and the optional `year` parameter; otherwise it does not extend parameter meaning beyond the schema. Baseline 3 applies.

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?

Opens with a specific verb and resource — 'Calculates one slow-planet transit against a birth chart, with exact dates' — then enumerates the four supported transit types that map one-to-one onto the `transit` enum. An agent can tell this is a targeted transit calculator rather than a general chart tool.

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 closing sentence gives concrete user-question triggers ('their Saturn return', 'where Jupiter is transiting for them this year', 'Mercury retrograde for their chart'), which is strong when-to-use guidance. It stops short of exclusions: no mention of when to prefer the sibling `get_personal_transits`, `get_sade_sati`, or `get_year_ahead` instead.

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