Methodology v2
Fruitful Significators
get_fruitful_significators
Get fruitful significators for an event, meaning planets that appear in BOTH the 4-level significator matrix AND the Ruling Planets of the MOMENT OF JUDGEMENT (KP Reader 4: the planets ruling the moment the matter is judged), which is 'judgement_datetime', default now, at the birth place unless a judgement place is given. L1/L2 (strongest) are prioritized over L3/L4. Returns the fruitful set plus 'rpMoment', 'judgement' (the instant, place and RP set used), 'rulingPlanetsAtBirth' and 'atBirth', the same filter with the BIRTH Ruling Planets, labelled for rectification only. Essential for precise KP timing: only fruitful significators can deliver event results. 'strictSelection' reports KP's selection rule beside the list, never subtracting from it: clause 1, posited 6/8/12 to the matter, and clause 2, in the sub of a planet in a detrimental house, are Astrology for Beginners canon p.318 verbatim; clause 3 (signifies ANY house 6/8/12 from ANY required house) extends a Reader 5 election rule and rejects 86.4% of fruitful significators and every node row on the 48-chart spread ('scripts/bp019-dasha-sublord.ts'), so read it as contested. 'find_event_timing_v2' applies clauses 1 and 2 only, to the period lords. 'fruitfulSignificators' is KSK's list in its L1 to L4 order; the per-entry 'tiebreak' and 'rankedFruitfulSignificators' are Sunil Gondhalekar's Four Step ordering (the sub lord's star lord), not KSK's, and 'methodSeams' points at get_four_step_fruitful_ranking, which carries them under his name. **Node rule, three stated variants.** 'nodeRuleVariants' gives the moment's Ruling Planets under each rule for Rahu and Ketu, each with its methodology (what it does, source class, locus, how it differs) and the fruitful list it selects: 'none', the default this list uses (KSK's worked RP examples name no node, Reader 6 canon pp.138, 211; no page states it for fruitful selection, F166); 'books-substitute-when-alone', get_ruling_planets' default (Astrology for Beginners canon p.318, the fruitful-selection paragraph itself: a node in a ruling planet's sign is included, and preferred to the planet when alone); 'web-always-add' (added beside the planet, KSK's own Reader 6 canon p.132). A node rule changes the fruitful list on 59.7% of chart-event-moments ('scripts/f166-node-rule-fruitful.ts'). 'judgement.holdsUntil' is the next instant those Ruling Planets change, solved and never a score: 'instant' in UTC, 'local' with the offset in force then only when 'judgement_time_zone' is sent, otherwise with the judgement's own offset (read 'utcOffsetSource'), and 'changes' naming the member (the Ascendant's or the Moon's sign or star lord, or the day lord at sunrise at the place) with its old and new lord. The fruitful set holds until that instant; say so when you quote it. Name the rule you quote; the default list is unchanged.
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. |
| judgement_datetime | string | No | The moment the matter is judged, local wall clock at the birth place unless judgement_latitude/longitude are given (e.g. 2026-09-27T12:00:00). Defaults to now. KP selects fruitful significators with the Ruling Planets of THIS moment (KP Reader 4), not the birth moment. |
| judgement_latitude | number | No | Latitude of the place of judgement. Defaults to the birth latitude. |
| judgement_longitude | number | No | Longitude of the place of judgement. Defaults to the birth longitude. |
| judgement_utc_offset_minutes | number | No | UTC offset of the place of judgement in minutes. Defaults to the birth offset when the place defaults to the birth place. |
| judgement_time_zone | string | No | IANA time zone of the place of judgement (e.g. "Asia/Colombo"), instead of judgement_utc_offset_minutes: the offset in force there at judgement_datetime is read from the tz database. If both are given they must agree. |
| event | event name | No | Event to find fruitful significators for. If omitted, the engine derives the most active event from the running MD+AD lord's signification with Ruling Planets tie-break, and returns it in the eventResolution field. Ignored if house_group is provided. |
| house_group | array<house number (1-12)> | No | Override event lookup with explicit house numbers (1-12). When provided, event is ignored. |
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_fruitful_significators",
"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.