Event timing

Horary Chart (v2)

get_horary_chart_v2

Enhanced KP horary chart with Moon connectivity validation. If query_event is provided, validates whether Moon signifies the relevant houses. If the Moon is disconnected, 'predictionAvailable' is false and a 'withhold' block is returned under the Moon gate: the successor literature reads a disconnected Moon as a question not yet settled in the querent's mind (source class 'later': L. P. Bhargava, Astrology & Athrishta 1967, the earliest; K. Subramaniam, Astro Secrets and KP Part II, canon pp.600 and 603). No KSK page withholds a horary on the Moon (Q045): KSK reads the Moon to name the query (Reader 6 canon pp.177-179, 204-205) and judges the querent's number as given, keeping the same number on the day of judgement (canon p.322). The block carries 'source', 'kskPosition', 'remedies' and 'retryGuidance': Bhargava's re-ask (clarify the query, then another number at once), KSK's same number on the day of judgement, and a fresh number after some time, which is a rule for a failed prediction and not for the Moon (canon p.601). 'gateReadings' states three readings side by side, none picked, each with its 'system', 'source' and whether the chart 'proceeds': [KP-extended] the Moon gate, the one 'withhold' and 'predictionAvailable' follow; [KP-extended] the Moon or the Ascendant sub lord ('Hints for judging a Horary chart', canon p.603, less strict); [KP] KSK's, the number judged as given, which always proceeds. Say which reading you follow. Always provide query_event for proper KP horary analysis. Also returns 'numberMethods': what the number is checked against, as four stated methods side by side, each with its 'system', 'source' class and 'methodologyNote', none picked and none gating 'predictionAvailable'. [KP] KSK: the number is valid in itself, gated only by its range (Reader 6 canon pp.34-35, 114, 279); its lords among the ruling planets strengthen an RP, never test the number. [KP-extended] the Gulbarga short method (M. S. R. Murthy and H. Purushottama, Astrology & Athrishta 1971): the number's sub lord against the Ascendant and Moon star lords of the moment gives positive / probable (ask another number) / negative, with Reader 6's five counter-cases recorded beside it; the KP E-zine 2009 test (the Moon and the Ascendant cuspal sub lord must reflect the question, both readings of 'and'); Prabhakar c.2006's number ruling planets, disputed against Reader 6 canon p.211. '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'), so none is computed. Report each method under its own name. 'rulingPlanetsVariants' carries the two stated definitions of a number chart's ruling planets (F185), each with its 'system', 'source' and 'methodologyNote': [KP] KSK's, from the Ascendant RISING at the moment of judgement (Reader 6 canon p.211, number 100 is Leo while 'the lagna is Dhanus'), which 'chart.rulingPlanets' and every judgement here read; [KP-extended] Prabhakar c.2006's, from the number's sign and star lords, reported and never applied. Name which one you cite. Each of the two spreads is also a tool of its own, named in 'methodSeams': 'get_horary_number_methods' ('numberMethods') and 'get_horary_ruling_planets_variants' ('rulingPlanetsVariants'); both blocks still ship here. 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

Name	Type	Required	Description
ayanamsa	enum: kp \| kp_new \| lahiri \| raman \| true_chitra \| khullar	No	Ayanamsa system. Defaults to kp.
birth_datetime	string	No	Deprecated, 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.
latitude	number	No	Deprecated, use judgement_latitude.
longitude	number	No	Deprecated, use judgement_longitude.
utc_offset_minutes	number	No	Deprecated, use judgement_utc_offset_minutes or judgement_time_zone.
time_zone	string	No	Deprecated, use judgement_time_zone.
judgement_datetime	string	No	The 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_latitude	number	No	Latitude of the place where the question is judged, north positive.
judgement_longitude	number	No	Longitude of the place where the question is judged, east positive.
judgement_utc_offset_minutes	number	No	UTC 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_zone	string	No	IANA 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_number	number	Yes	KP horary question number (1-249)
query_event	string	No	Event being queried (e.g., 'Marriage', 'Career / Job Start'). Triggers the Moon connectivity check and `gateReadings`.
turned_for	number	No	Turn the chart for a third party: the house that stands for them (7 spouse, 5 child, 9 father, 3 younger sibling). Their kth house is the kth from it; returned as `turned`.

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