Advanced techniques

Punarphoo (Moon-Saturn marriage delay)

get_punarphoo

Punarphoo, KP Reader 4 ch.22: the natal Moon-Saturn tie that delays the date of a marriage and never denies it. Natal only, never read from an elected moment. Each party reads the sign-level form (astrology-for-beginners p.315) and the stronger star-and-sub form (Reader 4 p.82), the house clause recovered by Q008 (Saturn in 1, 3, 5, 7 or 10 without a tie to 2, 7 or 11 reads 'delay-or-denial', a contradiction inside the sources, reported and gating nothing) and K.R. Kar's Sun cancellations (reported, never applied). Reader 4 p.82 says to check BOTH horoscopes: pass 'person2' for the partner. Returns '{ partyA: { present, reasons, strength: none | sign-level | star-and-sub, houseClause: { saturnHouse, inObstructiveHouse, saturnSignifiesMarriageHouses, severity, note }, cancellation: { cancelled, reasons, note }, note }, partyB, presentInEither, presentInBoth, note }', plus 'framesUsed' when 'person2' is given. Without 'person2', 'partyB' is null and the response is the same block 'get_second_marriage' returns as 'punarphoo'.

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.
person2	object	No	The partner's birth chart. Optional. When given, Punarphoo is read in both charts, the test Reader 4 p.82 states.

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