Advanced techniques

Eclipse Impact on Natal Chart

get_eclipse_impact

Locates upcoming solar and lunar eclipses (next N months, default 24) and measures arc-distance from each eclipse degree to natal sensitive points. **THE ECLIPSE IS COMPUTED, NOT SCREENED**: shadow radii, semidiameters, parallax and gamma, so every event carries its 'kind' (solar partial/annular/total, lunar penumbral/partial/total), its 'magnitude', and 'greatestDateUTC', which is the instant of greatest eclipse and differs from the syzygy by up to hours. Verified against all 50 eclipses in NASA's 2000-2010 canon, types included: 24 of 24 solar and 26 of 26 lunar, zero false positives and zero misses. The node-limit filter that used to BE the answer is now only a fast path in front of the geometry. **'countsAs' IS THE FIELD TO READ AND NOTHING HERE DECIDES FOR YOU**: a penumbral lunar eclipse is an eclipse astronomically and very nearly nothing to the naked eye, so each event reports 'astronomical' (any penumbral contact), 'naked_eye' (excludes penumbral lunar) and 'umbral' (the Moon actually enters the dark shadow). Say which convention your reading used. The previous screen enforced the narrow one silently, by using the umbral limit, and so missed 27% of lunar eclipses. Measures arc-distance to natal sensitive points (Lagna, MC, all 9 luminaries / planets). Each natal hit gets a severity band: CRITICAL ≤1°, PROXIMAL ≤5°. Books: KP Reader 5, classical eclipse interpretation. Use to flag windows of intensified life themes; never frame as deterministic prediction.

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 begin scan from (default: now). 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.
scan_months	number	No	Months forward to scan (default: 24).

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_eclipse_impact",
    "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.