Advanced techniques

Sex of a Child as the Corpus States It (KP Reader 2 canon p.108, Reader 4 canon p.240)

get_child_sex_indication

Two statements the corpus makes, kept apart. The traditional general rule KSK prints in Reader 2: the 5th cusp's sign, the 5th lord's gender (BPHS ch. 3 v. 19: Sun, Mars, Jupiter male; Moon, Venus female; Mercury, Saturn neuter) and the sign it occupies, masculine for boys and feminine for girls, three testimonies counted and reported. And the one KP delivery case in Reader 4: the running antara and sookshma lords AT THE DELIVERY being male planets read a son, with KSK's own words carried, 'I never had any experience in pin-pointing the sex before birth'. Pass delivery_date to compute the second; without it the field says why it waits. The count of children is NOT computed: no Reader page searched states a number, and a count crosses the wire with its page or not at all. A disclaimer travels on the payload; nothing here is a verdict.

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.
delivery_date	string	No	ISO date of the delivery, known or expected, for the Reader 4 antara-and-sookshma read. Omit for the general rule only.

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