Advanced techniques

Second Marriage (KP T33)

get_second_marriage

KP second marriage (T33, renamed from get_marriage_advanced on 2026-10-08): the 8th cusp (2nd from the 7th) sub lord against houses 2, 8 and 11 for the promise, an estimate of the first marriage from the 7th CSL and the 2/7/11 MD-AD periods, and the MD-AD-PD periods after it whose lords signify 2, 8 or 11. Returns '{ secondMarriageEventDef, cslPromise: { eighthCSLPlanet, eighthCSLStarLord, housesSignified, housesRequired, coverage, verdict, starLordDenial, isPromised, notes }, firstMarriageEstimate: { found, earliestDate, latestDate, periods, periodsCap }, candidatePeriods: [{ startDate, endDate, mahadasha, antardasha, pratyantardasha, mdHouses, adHouses, pdHouses, jointCoverage, isAfterFirstMarriage, confidence, reasons }], overallVerdict: PROMISED | PARTIALLY_PROMISED | NOT_PROMISED, punarphoo, notes, summary, methodSeams }'. 'confidence' is an engine weighting. 'punarphoo' (the natal Moon-Saturn delay, KP Reader 4 ch.22) gates nothing here and is also a tool of its own, 'get_punarphoo', which takes the partner chart for the two-chart 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_second_marriage",
    "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.