Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Event timing

Horary Number Methods (KSK and successors)

get_horary_number_methods

What a horary number is checked against, as four stated methods side by side, each with its 'system', 'source', 'alsoAt' and 'methodologyNote', none picked and none gating anything. [KP] 'ksk-self-validating': the number is valid in itself, gated only by its range ('numberValid', 'rangeGates', Reader 6 canon pp.34-35, 114, 279); its lords among the ruling planets strengthen an RP, never test the number ('strengthening'). [KP-extended] 'gulbarga-short-method' (Murthy and Purushottama, Astrology & Athrishta 1971): the number's sub lord against the moment's ruling planets gives 'answerUnderThisMethod' positive / probable-ask-another-number / negative, with 'laterForms' and Reader 6's own 'recordedCases' set against it; 'kp-ezine-2009-radical': the Moon and the Ascendant sub lord must reflect the question ('evaluation', null without query_event, both readings of 'and'); 'prabhakar-number-rps' (c.2006): the number's lords as Ascendant ruling planets, 'disputedBy' Reader 6 canon p.211. Returns '{ questionNumber, numberLords, momentRulingPlanets, methods[4], unsourcedClause, note }'. 'momentRulingPlanets' are taken from the Ascendant RISING at the moment, not the number's. No source makes the number's agreement with the ruling planets a validity test ('unsourcedClause'). Report each method under its own name. The same block 'get_horary_chart_v2' and 'get_horary_number_intuition' return as 'numberMethods'; given the same moment of judgement, the three cast the same chart. The chart is cast at the moment and place the question is judged: send 'judgement_datetime' (the local wall clock there), 'judgement_latitude', 'judgement_longitude', and 'judgement_utc_offset_minutes' or 'judgement_time_zone'. This tool needs no birth data. The result echoes 'horaryMoment' ('instant', 'local', 'place', 'source', 'utcOffsetSource') and 'deprecatedInput', which names any old field name the call used and the field to send instead.

Parameters

NameTypeRequiredDescription
ayanamsaenum: kp | kp_new | lahiri | raman | true_chitra | khullarNoAyanamsa system. Defaults to kp.
birth_datetimestringNoDeprecated, use judgement_datetime. For this one release, a call with no judgement_* field is cast at this date and time and the place below, and the result's deprecatedInput says so.
latitudenumberNoDeprecated, use judgement_latitude.
longitudenumberNoDeprecated, use judgement_longitude.
utc_offset_minutesnumberNoDeprecated, use judgement_utc_offset_minutes or judgement_time_zone.
time_zonestringNoDeprecated, use judgement_time_zone.
judgement_datetimestringNoThe moment the question is judged, as the local wall clock at the place of judgement, ISO 8601 with no zone suffix (e.g. 2026-10-20T10:30:00). Send it on every call; the result's horaryMoment echoes it.
judgement_latitudenumberNoLatitude of the place where the question is judged, north positive.
judgement_longitudenumberNoLongitude of the place where the question is judged, east positive.
judgement_utc_offset_minutesnumberNoUTC offset in force at the place of judgement at that moment, in minutes east of UTC (e.g. 330 for India, -240 for New York in summer). Prefer judgement_time_zone, which works it out; if both are given they must agree.
judgement_time_zonestringNoIANA time zone of the place of judgement (e.g. "Asia/Colombo", "America/New_York"). The offset in force there at judgement_datetime is read from the tz database, daylight saving and past changes included.
target_numbernumberYesKP horary question number (1-249)
query_eventstringNoEvent being queried (e.g., 'Marriage', 'Career / Job Start'). Only the E-zine test reads it; without it that method's `evaluation` is null.
query_datetimestringNoDeprecated, use judgement_datetime.
query_latitudenumberNoDeprecated, use judgement_latitude.
query_longitudenumberNoDeprecated, use judgement_longitude.
query_utc_offset_minutesnumberNoDeprecated, use judgement_utc_offset_minutes or judgement_time_zone.

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_horary_number_methods",
    "arguments": {
      "judgement_datetime": "2026-10-20T10:30:00",
      "judgement_latitude": 6.927,
      "judgement_longitude": 79.861,
      "judgement_time_zone": "Asia/Colombo",
      "target_number": 137
    }
  }
}