Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Advanced techniques

Rasi Drishti, sign-to-sign aspect [Jaimini, BPHS ch. 8 v. 9]

get_rashi_drishti

[Jaimini adjunct] The sign-to-sign aspect Jaimini and BPHS ch. 8 v. 9 share: a movable sign aspects the three fixed signs other than the one next after it, a fixed sign the three movable signs other than the one next before it, a dual sign the other three dual signs; symmetric. Returns for every sign the signs it aspects, the planets aspecting it and its occupants on this chart. This is the rule under the arudha aspects and the Drig dasha; it had been computed inside get_arudha_lagna since F050 corrected it and reachable from nothing else. Not the graha drishti of the planets.

Parameters

NameTypeRequiredDescription
birth_datetimestringYesBirth date and time in ISO 8601 format (e.g., "1990-05-15T14:30:00").
latitudenumberYesBirth location latitude. Range: -90 to 90.
longitudenumberYesBirth location longitude. Range: -180 to 180.
utc_offset_minutesnumberYesUTC offset in minutes (e.g., 330 for IST, -300 for EST).
ayanamsaenum: kp | kp_new | lahiri | raman | true_chitra | khullarNoAyanamsa system. Defaults to kp.

Example call

Send the request as a standard MCP tools/call:

http
POST https://mcp.lumin.guru/mcp
Authorization: Bearer mcp_yourkey...
Accept: application/json, text/event-stream
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_rashi_drishti",
    "arguments": {
      "birth_datetime": "1992-08-14T04:32:00",
      "latitude": 6.927,
      "longitude": 79.861,
      "utc_offset_minutes": 330,
      "ayanamsa": "kp"
    }
  }
}

Birth data

This tool requires birth data on every call. The MCP server is stateless, so calling set_birth_profile first validates the data and returns the reading plan, but it does not store anything. Repeat the same five fields here.