Advanced techniques

Where the Partner Comes From (KP Reader 4, direction and locality of the partner)

get_spouse_locality

KP Reader 4's rule for where the partner comes from, on the natal chart: the sub lord of the 7th cusp sub lord (and of each 7th-house significator) and the houses that sub lord OWNS. Owning the 1st or 4th: a co-tenant, one's own street, town or district, no journey after marriage. Owning the 3rd: a cousin, a neighbour, a short land journey, or a match fixed by correspondence or advertisement. Owning the 11th: a friend's family. Owning the 9th or 12th: a stranger, a love marriage, a foreigner, a long distance, which is the corpus's only statement on an inter-community or foreign partner. The extract of the page dropped its bare numerals, so every branch carries 'decodeConfidence' (the 3rd is certain from its suffix; the others are read from the page's sense) and the quote is given with its gaps. 'direction' applies Reader 6's sign-to-direction table to the sign the 7th cusp sub lord occupies and is labelled as a horary page applied natally; it gates nothing. Canon pages cited.

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