Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Advanced techniques

Retrograde Cuspal Sub Lord States (disputed double retrograde labelled)

get_retrograde_csl_states

[KP extended: one state is disputed inside the KP corpus] For each cusp of an event, whether its cuspal sub lord is retrograde and in whose constellation, read the way the pages read it: the sub lord's OWN star lord, with Rahu and Ketu never retrograde (KP Reader 6 canon pp.114, 155). States: NORMAL; STATE_A_DELAYED, retrograde in a direct planet's star, delay until it turns direct and passes its turning point (Reader 6 canon p.155, corpus); STATE_B_DENIAL, retrograde in a retrograde planet's star or its own, which is **disputed**: failure at Reader 6 canon p.155 and Astrology for Beginners canon pp.317-318, delay until the retrograde lord resumes direct course at Astro Secrets canon p.1379 (Astrology and Athrishta, September 1978), both quoted on the entry as 'positions'; STATE_C_SUDDEN, retrograde under 0.05 degrees a day, a labelled Lumin convention (F063). Returns '{ system, systemNote, event, requiredHouses, scope, entries: [{ house, cslPlanet, cslIsNode, cslEngineRetrograde, cslRetrogradeForRule, cslSpeed, cslStarLord, cslStarLordRetrogradeForRule, cslInOwnStar, cuspStarLord, state, stateLabel: { standing, note }, disputed, positions?, stateByCuspStarLord, explanation }], disputedCusps, keyingMoves, summary }'. 'stateByCuspStarLord' is get_retrograde_panel's old keying, so a move is visible. The pages are question charts: on a natal chart this gates no promise (R2). Present STATE_B as both readings, never as a denial.

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.
eventevent nameNoEvent whose cusps to read (default: Marriage). Ignored if house_group is provided.
house_grouparray<house number (1-12)>NoOverride event lookup with explicit house numbers (1-12).

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