Advanced techniques

Job Change vs Promotion (KP T35)

get_job_change_vs_promotion

KP job change vs promotion differentiation (T35, renamed from get_career_advanced on 2026-10-08): checks if 5th house (12th from 6th = end of current employment) is activated in the current antardasha. 5th active + 10th = job change. 10th+11th without 5th = promotion within same organization. One classification for the running period and one per upcoming period. Returns '{ scoreProvenance, currentDasha, currentOutcome: JOB_CHANGE | PROMOTION | UNCERTAIN, currentConfidence, currentReasons, adLordAnalysis, house5Significators, upcomingPeriods: [{ startDate, endDate, mahadasha, antardasha, pratyantardasha, outcome, confidence, reasons, mdAnalysis, adAnalysis, pdAnalysis }], summary }'; **'upcomingPeriods' is paged**. 'confidence' is an engine weighting labelled in 'scoreProvenance', and this reads 10 and 11 for promotion where KSK reads 2, 6, 10 and 11. The sourced siblings: 'get_promotion_verdict' (the orthodox promotion gate) and 'get_job_change_timing' (dated job-change windows on the 10th CSL promise test).

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