Advanced techniques
Parashari dasha lords: facts and MD-AD geometry, no verdict [Vedic Parashari]
get_parashari_dasha_lord
[Vedic Parashari] Parashari, not KP. The running Vimshottari mahadasha, antardasha and pratyantardasha lords at 'query_date' (default now), read by the Parashari checklist the curriculum names, each fact carrying the provenance of the module that computed it: (a) natural nature (BPHS ch. 34 vv. 8-10, the Moon by phase, Mercury by company), (b) functional nature by lagna, the printed ch. 34 table AND the vv. 2-17 rule side by side, with yogakaraka and maraka, (c) whole-sign placement and the bhavas it owns, (d) the BPHS ch. 27 Shadbala in virupas against the planet's own requirement (never the 0-100 index) and the ch. 45 avasthas, (e) where it stands from the lagna lord, (f) the kendra-trikona LORDSHIP yogas it is part of (Laghu Parashari 14-22 and 18; for a node BPHS 34.17's yogakaraka test), (g) navamsa sign, lord, bhava from the navamsa lagna and vargottama, (h) nakshatra lord and sign dispositor, plus 'vargaLagna', the lord in the 6th, 8th or 12th from the D-10 lagna under both D-10 readings, labelled MODERN (Nemani 2004, Kumaran 2023; no classical locus). For consecutive lords (MD-AD, AD-PD) it returns the whole-sign count from one to the other and back, its class (same sign, kendra, trikona, 2/12, 6/8, 3/11), and natural and temporal friendship reported separately (the compound table is disputed between editions). On the MD-AD pair 'valence' is FIVE STATED READINGS, each with its method note, class and locus, never combined: BPHS pair by pair (San 52-60 / GCS 54-62: the AD lord in a kendra, trikona, 11th or 3rd from the MD lord favourable, 6th, 8th or 12th adverse; the 2nd DISPUTED inside BPHS, favourable in ten verses and adverse at San 59.41, shipped as 'both-stated'), Uttara Kalamrita 6.22 (mutual 6/8 adverse, else good), Phaladeepika 20.29 (6th, 8th or 12th from the MD lord adverse, else good), Phaladeepika 20.28 (the bhukti of the MD lord's or the lagna lord's enemy adverse, each clause tested), and Laghu Parashari 29-31 (relational, no valence: whether the MD lord gives its own results in this bhukti). NO TEXT STATES A MUTUAL 2/12 RULE, so none ships; the AD-PD pair carries no reading because every verse is MD-AD. THERE IS NO OVERALL GOOD OR BAD VERDICT: where the readings disagree, say so and name them. Read each label against 'baseRate' (200 charts, 'scripts/bp025-md-ad.ts'): the MD-AD pair is 6/8 or 2/12 for 30.4% of a life, BPHS and Phaladeepika 20.29 call 21.4% adverse, Uttara Kalamrita 12.5%, the disputed 2nd is 8.9%. Rahu and Ketu as lords carry no Shadbala and no functional row; 'nodeActsThrough' gives the bhava occupied and the conjunct lords (BPHS 34.16), the aspects received (34.17), the dispositor with its classical strength (Uttara Kalamrita 6.16, 6.21), and the aspects cast under every stated node-drishti reading (F175), each with its class. Not computed, and named: named yogas, the compound friendship. **'lords' and 'pairs' are paged together, one lord per page**: page 1 is the mahadasha lord with the MD-AD pair, page 2 the antardasha lord with the AD-PD pair, page 3 the pratyantardasha lord (its 'pairs' empty, and the note says so); 'dasha', 'baseRate', 'houseConvention', 'notComputed' and 'source' repeat on every page. Read all three pages before stating anything about the period. Gates no KP 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. |
| query_date | string | No | ISO 8601 date-time at which to read the running lords. Defaults to now. Must fall within 120 years of birth. Send a zone (Z, or +hh:mm as in 2026-10-20T10:30:00+05:30). A value without a zone is read as UTC, never as local time, and a date alone is midnight UTC. This is a different moment from judgement_datetime, which is a local wall clock sent with its own offset. |
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_parashari_dasha_lord",
"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.