Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Core analysis

Cuspal Sub Lord Condition (extent, eclipsed star, motion)

get_csl_condition

[KP] The condition of each of the twelve cuspal sub lords (CSLs), reported and gating nothing: the promise verdict is decided by signification alone ('motion_policy' says why, with KSK's pages). Returns '{ chart_info, cusp_conditions: [{ house, csl_planet, csl_extent, csl_combust_star, csl_motion_status }], motion_policy }', twelve rows. 'csl_extent' grades how much of a promise the cusp carries from the dignity of the CSL's star lord (KP Reader 6 canon p.265): '{ planet, planetDignity, starLord, starLordDignity, extent: MOST_SATISFACTORY|SATISFACTORY|ORDINARY|LESS|UNGRADED, gatesVerdict, gradeProvenance, reading, source }', where 'gradeProvenance' says which grades are KSK's words and which the engine's fill. 'csl_combust_star' says whether the CSL stands in a combust (eclipsed) planet's star and, if so, that cusp's result from Reader 6 canon pp.160-161: '{ planet, starLord, starLordCombustion, standsInCombustStar, cuspResult, timing, gatesVerdict, source }'. 'csl_motion_status' is '{ retrograde, combustion: NONE|ORDINARY|FULL, dignity, gates_verdict, delay_signal, note }', and on a retrograde CSL also 'delay_release: { turnsDirect, passesStartingPoint, note }': the natal reading (delivers when it turns direct, Astrology for Beginners canon p.885) and the horary one (Sutra 32, Reader 6 canon p.155, direct and past the degree it turned from), both dated and neither chosen; null for the nodes, which never turn. Retrogression is a delay at the timing phase, never a denial. Use it to read the cusp behind a verdict once rather than on every event row. The same block 'analyze_natal_promise' returns on every event row as 'extent', 'combustStar' and 'motion', keyed there by the event's 'house', with 'motion_policy' once.

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