Advanced techniques
Yoga Karaka (Lagna-specific) [Parashari]
get_yoga_karaka
[Parashari] Yoga karaka by lagna, as BPHS ch. 34 names it (Santhanam; ch. 36 in Sharma), read from the verses. The KP corpus does not use the concept, so never present it as a KP rule. BPHS gives two definitions: the pair rule (34.11-12, a kendra lord and a kona lord in exchange, together, one in the other's sign or in full mutual aspect) and the single-planet rule (34.13, one planet owning both a kendra and a kona), and 34.15 denies the yoga where the lords also own an evil house. Its per-lagna verses name a single planet for Taurus, Cancer, Capricorn and Aquarius, a PAIR (the 9th lord with the 10th lord) for Virgo, Libra, Scorpio, Sagittarius and Pisces, and none for Aries, Gemini and Leo. Returns 'yogaKaraka' (one planet, null where none is named) with 'yogaKarakaSource'; 'yogaKarakaPair' (the pair, never split into a primary and a secondary, with whether the two are related in this chart, reported and gating nothing); 'bphs' (what the verse names and the planets it calls auspicious, neutral or killers); 'readings' (every stated reading, the verse first: Leo Mars and Libra Saturn are derived from 34.13, and Libra and Aquarius are disputed, so give both readings); 'lagnaLord' (the lagna lord does not count on its own at the verse, and the later and modern readings that count it are listed apart); 'tableVariant' (this tool's earlier fixed table, whole, with the names no text supports marked unsourced); 'definitions'; 'placement' (KP house and whole-sign house); whether the running mahadasha or antardasha lord is a named yoga karaka (either member of a pair); 'rationale'; and 'definitionCheck' (sign-lordship arithmetic). 'secondaryYogaKaraka' is retired and always null. Say which reading you used.
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. |
| query_date | string | No | The moment the running mahadasha and antardasha are read for (default: now), which sets the dasha activation status. Send a zone (Z, or +hh:mm as in 2026-10-20T10:30:00+05:30). A value without a zone is read as UTC, never as local time, and a date alone is midnight UTC. This is a different moment from judgement_datetime, which is a local wall clock sent with its own offset. |
Example call
Send the request as a standard MCP tools/call:
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_yoga_karaka",
"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.