Advanced techniques

Eclipse-on-Sub-Lord Activation

get_eclipse_sublord_activation

Cross-references upcoming solar and lunar eclipses with natal cusp sub-lord boundaries. Eclipses landing within 30 arc-minutes of a cusp = CRITICAL activation of that house's significations; within 30 arcmin of a sub-lord boundary = STRONG. Activation window = eclipse date + 6 months. Use to identify specific cusps the next ~18 months will activate.

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 \| lahiri \| raman \| true_chitra	No	Ayanamsa system. Defaults to kp.
as_of	string	No	Reference date for the scan (default: now).
scan_months	number	No	Scan window in months (default: 18).
contact_threshold_arcmin	number	No	Minimum arc-min to keep a contact in output (default: 60).

Example call

Send the request as a standard MCP tools/call:

http

POST https://mcp.lumin.guru/mcp
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_eclipse_sublord_activation",
    "arguments": {
      "birth_datetime": "1992-08-14T04:32:00",
      "latitude": 6.927,
      "longitude": 79.861,
      "utc_offset_minutes": 330,
      "ayanamsa": "kp"
    }
  }
}

Engine endpoint

This tool delegates to the kp-engine endpoint:

http

POST /v1/kp/eclipse-sublord-activation

The engine is a private internal service. All public access flows through the MCP server, which handles auth, rate limiting, and response compaction.

Birth data

This tool requires birth data. If you have already called set_birth_profile in the same conversation, the MCP server injects those fields automatically and you can omit them from the call.