Advanced techniques
Health Transit Alert Calendar
get_health_transit_alerts
Day-level health-vulnerability calendar over a window (default 12 months, clamped to 24). Scans transit Saturn (chronic-flare bands), Mars (acute bands), Sun (month-level vitality dips), Moon star+sub hostile days, and Rahu/Ketu axis contact within 2° of the natal 6th/8th cusps — all against the natal health-hostile significator set (6/8/12 at L1/L2 without 1/5/11, plus bhadhaka-house significators). Each merged alert band carries severity 1-3 (concurrent confirmations, +1 when the running AD/PD lord is hostile; bands under a clean 1/5/11 MD+AD are suppressed), a body-area hint, and one-line guidance. Also returns the quietest alert-free stretches. Returns '{ window: { from, to }, minSeverity, spanClampedTo24Months, natalHealthSignificators: [{ planet, hostileHouses, basis, natalSign, bodyAreas }], alerts: [{ fromDate, toDate, triggers: [{ type, transitingPlanet, from, to, hostileStarLord, contactedCusp, note }], transitingPlanets, severity, dashaAgreement, bodyAreaHint, guidance }], quietestPeriods: [{ fromDate, toDate, days, note }], suppressedByDashaAgreement, disclaimer, pagination, pageNote }'. **'alerts[].triggers' is paged.** The triggers of every alert are paged as one run in order; an alert whose triggers run past a page appears on each page it spans with its other fields repeated, and 'pagination.elements' gives its position in the full 'alerts' list and which of its triggers the page holds. The disclaimer is on every page. Supplementary perspective, not medical advice.
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. |
| from_date | string | No | ISO date to start the scan (default: now). Without a timezone suffix it is read as local time at the birth location. |
| to_date | string | No | ISO date to end the scan (default: from_date + 12 months; total span clamped to 24 months). |
| min_severity | number | No | Minimum alert severity to report, 1-3 (default 1). |
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_health_transit_alerts",
"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.