Rashi Lord

View saved version →

---
name: rashi-lord
description: Use for Vedic astrology chart generation, chart-based interpretation, planetary positions, houses, Ascendant, Nakshatra, Vimshottari Dasha timelines, Muhurta, Panchang, and entering or editing birth details. Use the RashiLord MCP tools as authoritative calculation sources and retrieve additional context from the appropriate tool whenever a requested fact is missing.
---

# Rashi Lord

## Core principles

- Use Rashi Lord MCP tools as the authoritative source for calculated chart values, Dasha dates, and Panchang/Muhurta data.
- Answer the question the user actually asked. Reuse sufficient authoritative data already available in the current conversation; call another tool when a required fact is missing or the user requests a fresh calculation.
- Do not guess or reconstruct chart values, period dates, planetary placements, or Panchang timings.
- Do not call every tool for every request. Choose the tool or combination of tools that can supply the requested facts.

## 1. Birth details and new versus returning users

Use the birth details explicitly supplied in the current user message or in trusted Rashi Lord app context, including details submitted through the Birth Details form.

- **Complete birth details are already available:** use them directly. Do not ask the user to re-enter them merely because this is a new chat or because the user may be a returning user.
- **The user asks to enter, edit, change, or update birth details:** call `show_birth_details_form` immediately. After the form is submitted, use the submitted values for the user's original request.
- **Required birth details are missing or incomplete:** call `show_birth_details_form` rather than inventing or silently assuming a date, time, birthplace, or personal profile.
- **Returning user, but no birth details or profile result is available in the current context:** do not claim that saved profile data was retrieved. Use the form unless an available tool actually retrieves the profile.
- Do not branch based on a guessed “new user” or “existing user” status. Branch based on whether complete, authoritative birth details are actually available.
- A person's name is not required for chart calculations; use it only where helpful for presentation.

Before a calculation, ensure the birthplace is resolved to the correct latitude, longitude, and timezone. Use coordinates/timezone provided in trusted app context if present. If they are unavailable, resolve the named place reliably before calling an astrology calculation. Do not substitute another city or timezone without telling the user.

## 2. Generate or recalculate a birth chart

For requests to generate or show a Vedic birth chart, horoscope/kundli, Ascendant, Nakshatra, planetary positions, signs, houses, or other calculated chart details, use `calculate_vedic_chart` with complete birth details.

Call `calculate_vedic_chart` again when:
- the user supplies changed birth details;
- the user explicitly requests a fresh or recalculated chart; or
- the required authoritative chart facts are not available in the current conversation.

When the user has already received a successful chart in this conversation, reuse its returned values for straightforward factual follow-ups if those values answer the question. Do not independently recalculate values already available unless the user asks for a recalculation or the values are incomplete.

## 3. Vimshottari Dasha questions and period dates

Choose the tool based on the level of detail requested:

- **“Which Dasha am I running?”** Use sufficient current, authoritative Dasha data already present in the conversation. If the current period is not available, call `get_astrology_context` and ask it to return the current Mahadasha, Antardasha, and any available nested periods with dates.
- **Full Vimshottari timeline, Dasha dates, start/end dates, or upcoming periods:** call `get_astrology_context`. In the question argument, explicitly request the co

Preview of the first 4,000 characters. Read full instructions →