Skip to main content
Glama

Moon Dasha Vedic Astrology

Planetary positions

planetary_positions
Read-onlyIdempotent

Calculate where the planets stand in the sidereal zodiac at a moment with Moon Dasha: the nine grahas with sign, degree, nakshatra and pada, dignity, retrograde and combust, when each entered its sign and when it leaves; the retrograde run of Mercury to Saturn, current or next; the ascendant when a place is given; the Moon's tithi, phase and how much of it is lit. Default: now. For another moment give a date (and a time), on the clock of the place (a place_id from find_place) or of a time_zone alone; UTC when neither is given. Set outer_planets only when the reader asks about Uranus, Neptune or Pluto. The figures are Moon Dasha's calculations. Interpret them with care and never predict death, illness, a child's sex, markets, elections or court cases.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "planetary_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoThe day, YYYY-MM-DD, on the clock of the place or time_zone (UTC without either). Leave out date and time for now.
nodeNoRahu and Ketu by the mean node (default) or the true node.
timeNoThe time of day on that clock, 24-hour HH:MM. Default 12:00 when a date is given; with no date, today at that time.
ayanamsaNoDefault Lahiri. Krishnamurti is the KP ayanamsa.
place_idNoThe place_id find_place returned, for the ascendant and the local clock. Optional: without a place the answer has no ascendant.
time_zoneNoIANA time zone, e.g. "Asia/Kolkata", for its clock alone, without a place or an ascendant. Leave it out when giving a place_id, whose own clock is used.
outer_planetsNoAlso list Uranus, Neptune and Pluto. Set it only when the reader asks about them.

Output Schema

NameRequiredDescriptionDefault
linkYes
moonYes
clockYesWhose clock the times are on: the place's, a time zone's, or UTC when neither was given.
placeYes
is_nowYes
momentYesISO 8601 on the answer's clock, with its offset.
planetsYes
calendarYes
settingsYes
ascendantYesThe lagna; null without a place.
skipped_timeYesThe time asked for when the clock skipped it that day (the clocks went forward): the moment is that instant, read after the change.
noon_by_defaultYesA date was given without a time, so the moment is 12:00.

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 establish readOnly, idempotent and closed-world, so the safety profile is covered; the description adds real context beyond that: the results are Moon Dasha's own calculations, timezone defaults to UTC when neither place nor zone is given, and an explicit interpretive constraint against predicting death, illness, a child's sex, markets, elections or court cases. It does not discuss precision, limits or how the retrograde run window is bounded, so not 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?

Front-loaded with the verb and output inventory, and every clause concerns a real behavior (defaults, clock source, opt-in outer planets, interpretation limits). The middle section is a dense semicolon chain that partly duplicates schema text, which keeps it from being maximally concise.

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 an output schema present, the description needn't explain return values, and it covers defaults, clock resolution and the interpretive guardrail well. The remaining gap is that ayanamsa (a result-changing choice with a default of Lahiri) and the mean-versus-true node are left entirely to the schema, which matters for a calculation tool.

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 date, time, place_id, time_zone, node, ayanamsa and outer_planets. The description restates the date/time defaults and the place_id-versus-time_zone exclusivity rather than adding new meaning, and it never mentions ayanamsa or node selection, which materially change the figures. Baseline 3 is correct.

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 ("Calculate where the planets stand in the sidereal zodiac at a moment") and then enumerates the exact outputs: nine grahas with sign, degree, nakshatra/pada, dignity, retrograde/combust, ingress and egress, retrograde runs, ascendant, and tithi/phase. That enumeration plus the "Default: now" scoping makes it distinguishable from a natal or transit tool 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?

Gives concrete when-to-use rules: default is now, supply date (and time) for another moment, place_id versus time_zone for the clock, and outer_planets "only when the reader asks about Uranus, Neptune or Pluto" — an explicit when-not. It does not name an alternative sibling tool (e.g. transits or birth_chart) or say when a different tool should be chosen 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