Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Advanced techniques

Financial Loss Periods

get_financial_loss_periods

T28: the L1 and L2 significators of the 8th and 12th, the dasha periods whose Mahadasha, Antardasha and Pratyantardasha lords all signify a loss house, ranked by 'confidence' (a Lumin weighting of the houses covered, not a probability), and the Moon transit risk windows over the first 90 days of the first-ranked period, where the transit Moon's star and sub lords are both loss significators. Returns '{ lossHouses, l1l2Significators: [{ planet, level, houses }], lossDashaPeriods: [{ startDate, endDate, mahadasha, antardasha, pratyantardasha, mdHouses, adHouses, pdHouses, jointCoverage, confidence, reasons }], moonTransitRiskDates: [{ startDate, endDate, moonStarLord, moonSubLord, matchedSignificator, riskLevel }], notes, summary, pagination, pageNote }'. **'lossDashaPeriods' and 'moonTransitRiskDates' are paged together**: page N carries the Nth page of each, and a list that ends first is empty on the later pages, which 'pageNote' names. The same block 'get_financial_analysis' returns as 'lossConfirmation'.

Parameters

NameTypeRequiredDescription
birth_datetimestringYesBirth date and time in ISO 8601 format (e.g., "1990-05-15T14:30:00").
latitudenumberYesBirth location latitude. Range: -90 to 90.
longitudenumberYesBirth location longitude. Range: -180 to 180.
utc_offset_minutesnumberYesUTC offset in minutes (e.g., 330 for IST, -300 for EST).
ayanamsaenum: kp | kp_new | lahiri | raman | true_chitra | khullarNoAyanamsa system. Defaults to kp.

Example call

Send the request as a standard MCP tools/call:

http
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_financial_loss_periods",
    "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.