Chart and reference

Planet Relationships (Parashari)

get_planet_relationships

[Vedic Parashari, non-KP reference] The five-fold friendship between every pair of planets: the natural (permanent) relationship each way, the temporary one from their house positions (counted here by Placidus house), and the composite (MAHA_MITRA / MITRA / SAMA / SHATRU / MAHA_SHATRU), with a conjunction check at 10 degrees. KP judges by the stellar signification chain, not by friendship, so never let this decide a KP verdict. Returns '{ summary: { total_pairs, maha_mitra_pairs, mitra_pairs, sama_pairs, shatru_pairs, maha_shatru_pairs }, relationships: [{ planet_a, planet_b, permanent_a_to_b, permanent_b_to_a, permanent_mutual, temp_a_to_b, temp_b_to_a, temp_mutual, composite_a_to_b, composite_b_to_a, house_a, house_b, house_count_a_to_b, house_count_b_to_a, is_in_same_house, is_conjunct, conjunction_orb, interpretation }], pagination, pageNote }'. **'relationships' is paged.** The same block 'get_nakshatra_details' returns as 'planet_relationships'.

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