Transit and timing
Ruling Planet Intervals
get_rp_interval
Ruling Planets (RP) computed at regular intervals over a window (e.g. every 60 min for 24 h), judged at a PLACE: the Ascendant's sign and star lords and the day lord depend on where the judgement is made, so latitude, longitude and utc_offset_minutes are required and name the place of judgement (usually where the querent or astrologer is, not the birth place). Naive datetimes are the local wall clock there. The day lord runs sunrise to sunrise at the place (KP Reader 6); the midnight lord rides beside it as 'civilDayLord'. Returns '{ place, intervals: [{ datetime, localDatetime, weekdayLord, moonSignLord, moonStarLord, ascSignLord, ascStarLord, ranked[], civilDayLord, dayLordDiffersFromCivil }], variant, nodeRule, provenanceNote, dayLordConvention, pagination, pageNote }'. 'variant', 'nodeRule', 'provenanceNote' and 'dayLordConvention' are identical on every sample, so they are returned once at the top rather than repeated per row. **Paged.** Use when: scanning a day or week for the moment whose RP set best matches a target event's significators.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| startDatetime | string | Yes | Start datetime, local wall clock at the place of judgement (e.g. 2026-09-27T06:00:00) |
| endDatetime | string | Yes | End datetime, local wall clock at the place of judgement |
| interval_minutes | number | No | Interval between checks in minutes. Default: 60. |
Example call
Send the request as a standard MCP tools/call:
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_rp_interval",
"arguments": {
"startDatetime": "...",
"endDatetime": "..."
}
}
}