Advanced techniques
Sade Sati Sub-Lord Intensity Timeline
get_sade_sati_intensity
Sub-lord-resolved timeline for Saturn's sade-sati transit (the 7.5 year period of Saturn through 12th/1st/2nd from natal Moon), the fine-grained companion to 'get_sade_sati_phases'. Returns per-window '{ startDate, endDate, starLord, subLord, phase, saturnSign, starLordReading, subLordSignifications, subLordAdverse, subLordBenefic }' plus 'verdictCounts'. Read each window on two levels per KP Reader 5 canon p.299: the STAR lord's house lordship in this chart decides what is offered (8 or 12 adverse per p.298, 10 or 11 benefic per p.297), and the SUB lord decides whether it is delivered. **There is deliberately no intensity score.** The previous version returned one, keyed to which planet the sub lord was, so Jupiter scored the same in every chart ever cast; canon p.298 reads a single Saturn transit past nine lagnas to opposite conclusions, because a planet acts through the houses it owns in THIS chart. Sub-lord houses are reported rather than scored because the corpus states that role and gives no arithmetic for it, so weigh them yourself and say you did. Use to map specific months of sade-sati to what is actually promised and whether it lands. Books: KP Reader 5 canon pp.297-299.
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. |
| scan_start | string | No | Scan range start ISO date (default: now). |
| scan_end | string | No | Scan range end ISO date (default: +8 years). |
Example call
Send the request as a standard MCP tools/call:
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_sade_sati_intensity",
"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.