Advanced techniques

Hora, 24 Unequal Planetary Hours (KSK's corrected hora)

get_hora_today

24 planetary hours per day, each ruled by one of 7 visible planets in Chaldean order (Saturn→Jupiter→Mars→Sun→Venus→Mercury→Moon). The hours are UNEQUAL: day horas are (sunset − sunrise) / 12 and night horas (next sunrise − sunset) / 12, which is KSK's correction of the almanac's fixed sixty-minute hour, with each hora subdivided among the seven planets (KP Reader 3 canon pp.524-527). KSK treats hora as a tie-breaker between moments that already pass the chart tests, never a reason to accept one ('kpStanding'). Day starts at sunrise; first hour = weekday's lord. Returns each hour's lord, quality, start/end UTC, interpretation, plus 'currentHora' for the moment you asked about. Pairs with Choghadiya (a Vedic muhurta table) for fine-grained timing. The astrological day runs sunrise to sunrise, so 'utc_offset_minutes' decides which civil day is meant and is required.

Parameters

Name	Type	Required	Description
latitude	number	Yes	Location latitude
longitude	number	Yes	Location longitude
utc_offset_minutes	unknown	Yes	no description
query_date	string	No	The moment to read, ISO 8601 (default: now). Pass the FULL datetime, not just a date, whenever the question is about what is running now: a bare date is midnight UTC, so `currentPeriod` would answer for midnight rather than for 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.

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_hora_today",
    "arguments": {
      "latitude": 0,
      "longitude": 0
    }
  }
}