Advanced techniques

Ruling Planets Panel (old name)

get_rp_advanced

[RENAMED, use get_ruling_planets_panel] The same tool under its old name, kept for one release so existing callers keep working. It returns exactly what get_ruling_planets_panel returns: strengthHierarchy and dashaSyncAnalysis read with the ruling planets of the moment of judgement ('judgement_datetime', default now), and the birth-set reading beside them as 'atBirth'.

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.
judgement_datetime	string	No	The moment the matter is judged, local wall clock at the birth place unless judgement_latitude/longitude are given (e.g. 2026-09-27T12:00:00). Defaults to now, and the result's `judgement` says so (`datetimeDefaultedToNow`). KP reads the ruling planets of THIS moment (KP Reader 4), not the birth moment; the birth set is reported beside it as `atBirth`.
judgement_latitude	number	No	Latitude of the place of judgement. Defaults to the birth latitude.
judgement_longitude	number	No	Longitude of the place of judgement. Defaults to the birth longitude.
judgement_utc_offset_minutes	number	No	UTC offset of the place of judgement in minutes. Defaults to the birth offset when the place defaults to the birth place.
judgement_time_zone	string	No	IANA time zone of the place of judgement (e.g. "Asia/Colombo"), instead of judgement_utc_offset_minutes: the offset in force there at judgement_datetime is read from the tz database. If both are given they must agree.
event	event name	No	Event name for RP-dasha sync analysis (default: Marriage). Ignored if house_group is provided.
house_group	array<house number (1-12)>	No	Override event lookup with explicit house numbers (1-12). When provided, event is ignored.

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_rp_advanced",
    "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.