Advanced techniques
Ashtama Sani and Ardha-ashtama, read by star lord
get_ashtama_sani
Saturn in the 8th sign from the natal Moon (Ashtama Sani, ~2.5 years) and in the 4th (Ardha-ashtama, also called Kantaka Sani), every window across the life, each decomposed into one entry per nakshatra Saturn crosses inside it. **The window is not the verdict.** KP Reader 5 devotes four chapters to saying so: Ch.42 "Is Chandra-Ashtama ever evil", Ch.43 "Chandrashtama and its truth", Ch.45 "Ashtama Sani and Honour", Ch.53 "Traditional Transit System - Meaningless". canon p.290: the blanket adverse reading "is incomplete", because "in which cases Sani is a benefic and in which cases Ashtama Sani is evil, has not been scientifically discussed elaborately"; canon p.286 heads a worked example "the honour and reputation conferred on a Hotel Proprietor and his success in the competition during Ashtama Sani". The KP verdict is chart-dependent and comes from 'starLordWindows[].reading', judged on that star lord's house lordship in THIS chart: signifying 8 or 12 is adverse (canon p.298), 10 or 11 benefic (canon p.297). 'currentStatus' says whether either is running now. A verdict of UNKNOWN means significators were unavailable, so report that there is no KP verdict rather than falling back on the window's name. Companion to 'get_sade_sati_phases', which returns these two families as dates only. Books: KP Reader 5 canon pp.277-290, pp.296-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. |
| query_date | string | No | ISO date to evaluate against (default: now). |
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_ashtama_sani",
"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.