Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Advanced techniques

Why a promised marriage comes off late

get_marriage_delay

The seven conditions KP Reader 4 chapter 21 lists under the heading "Marriage is Promised but it comes off late in life" (canon pp.76-79). Answers the question the promise and timing tools do not: not whether marriage happens or when, but WHY it keeps slipping. **Every condition here is a DELAY and none is a denial** — whether marriage is promised at all is decided by the 7th cuspal sub lord, never by this list. **Only three of the seven are computable and the response says which.** Four invoke Uranus or a Western square, neither of which exists in KP, so they are returned with 'computed: false' and a reason rather than silently skipped or half-scored. The three that are computed: Saturn in the 1st, 3rd, 5th, 7th or 10th sign from the Lagna or the Moon while owning none of 2/7/11; Mars in the 7th; Moon conjoined with Saturn. **This is the received tradition, not KSK's method**, and the response says so: 'system' is 'vedic-parashari-with-western-aspects', and 'kpPosition' points at Punarphoo, which is what KSK gives in the same chapter (canon p.79) as his own reading and which 'get_marriage_advanced' carries. 'courseOfEvents' quotes what the corpus says a delay looks like — proposals falling through one after another, the bride resolving to stay unmarried, then a fresh party and a sudden celebration — instead of inventing a severity score the page does not give. Note on the source: canon pp.76-79 render every digit one higher than it should be, and the house numbers above are decoded through that shift, confirmed against a birth date, a marriage date and a stated age that only reconcile under it. Books: KP Reader 4 ch.21, canon pp.76-79.

Parameters

NameTypeRequiredDescription
birth_datetimestringYesBirth date and time in ISO 8601 format (e.g., "1990-05-15T14:30:00").
latitudenumberYesBirth location latitude. Range: -90 to 90.
longitudenumberYesBirth location longitude. Range: -180 to 180.
utc_offset_minutesnumberYesUTC offset in minutes (e.g., 330 for IST, -300 for EST).
ayanamsaenum: kp | kp_new | lahiri | raman | true_chitra | khullarNoAyanamsa 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_marriage_delay",
    "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.