Advanced techniques

Sanjay Rath Karakamsa Spiritual Lens Workflow

run_karakamsa_spiritual_lens

Atomic spiritual / soul-purpose reading. Runs Atmakaraka identification → D9 → Karakamsa → 12th-from-Karakamsa → Ishta Devata + D20 + past-life karmic + Bhrigu Bindu in one call. Returns '{ atmakaraka, karakamsa, twelfthFromKarakamsa, ishtaDevata: { primaryDeity, mantra }, d20Spirituality, pastLifeSummary, bhriguBinduDestiny, houseFrames, spiritualPath, blockSystems[] }'. Jaimini-led: the D20 is Parashari, the past-life panel a later cross-system synthesis and the Bhrigu Bindu a modern construct, and 'blockSystems[]' names each. House numbers: 'wholeSignHouse' fields are the Jaimini (whole-sign) houses; 'natalHouse', 'saturnHouse' and 'bhriguBinduDestiny.house' are KP Placidus bhavas, as 'houseFrames' says. Pattern C. Per Sanjay Rath 'Crux of Vedic Astrology' + Jaimini Sutras.

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	ISO date (default: now). 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:

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": "run_karakamsa_spiritual_lens",
    "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.