Advanced techniques

Special Lagnas (BPHS ch. 5: Bhava, Hora, Ghati, Varnada; ch. 3: Pranapada)

get_special_lagnas

Parashari, not KP. The five special lagnas Brihat Parashara Hora Shastra constructs, each with its verses: Bhava Lagna, Hora Lagna and Ghati Lagna advance from the Sun's longitude AT SUNRISE at 6, 12 and 30 degrees per ghati of time elapsed since that sunrise (ch. 5 vv. 2-8); Varnada Lagna is a SIGN reached by the odd/even counting rule of ch. 5 vv. 10-13 from the natal lagna and the Hora Lagna, with the working shown; Pranapada is the natal Sun advanced 120 degrees per ghati with the fixed/dual sign offset of ch. 3 vv. 71-74. The day is sunrise to sunrise, so a birth before dawn measures from the previous sunrise. Each point carries its sidereal longitude, sign, whole-sign house and Sripati house. Sree Lagna and Indu Lagna are NOT in BPHS and are returned under 'notComputed' with the reason, rather than built from a summary and labelled Parashari. Hora Lagna and Ghati Lagna are the inputs to the Jaimini longevity lagna-pairs. Source is stated with the edition (Santhanam 1984). Nothing here gates a KP verdict.

Parameters

Name	Type	Required	Description
birth_datetime	string	Yes	Birth date and time in ISO 8601 format (e.g., "1990-05-15T14:30:00").
latitude	number	Yes	Birth location latitude. Range: -90 to 90.
longitude	number	Yes	Birth location longitude. Range: -180 to 180.
utc_offset_minutes	number	Yes	UTC offset in minutes (e.g., 330 for IST, -300 for EST).
ayanamsa	enum: kp \| kp_new \| lahiri \| raman \| true_chitra \| khullar	No	Ayanamsa 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_special_lagnas",
    "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.