Advanced techniques

Jaimini Chara Karakas (Atmakaraka → Darakaraka)

get_chara_karakas

[Jaimini adjunct] Chara karakas ranked by exact sidereal longitude within the sign (minutes, then seconds, decide): Atmakaraka (highest, soul) → Amatyakaraka (career) → Bhratri (siblings) → Matri (mother) → [Pitri (father), eight scheme only] → Putra (children) → Gnati (obstacles) → Darakaraka (lowest, spouse). Seven or eight is a live dispute the sutra itself leaves open, so BOTH lists are always returned ('sevenScheme', 'eightScheme' with Rahu at 30 − degree) with 'schemesDisagreeOn' naming the offices that change; 'karaka_scheme' picks which one fills 'karakas' (default seven, Sun to Saturn, no node). A tie is reported at the arc-minute (kala), never the whole degree, and 'tieReadings' carries each source's rule for it (seconds decide; Rahu fills the merged office; same-longitude planets share an office), none picked. Each karaka's 'wholeSignHouse' is the Jaimini house (whole sign from the lagna); 'house' is the KP Placidus bhava, kept for continuity. Used for soul-purpose / career-coaching B2B.

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.
karaka_scheme	enum: seven \| eight	No	Which scheme fills `karakas`, `atmakaraka` and `darakaraka` (default seven). Both lists are returned either way.

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