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 Moon is disconnected, the question is premature and prediction is flagged as unreliable. Always provide query_event for proper KP horary analysis.

Parameters

Name	Type	Required	Description
birth_datetime	string	Yes	Birth date and time in ISO 8601 format (e.g., "1990-05-15T14:30:00").
latitude	number	Yes	Birth location latitude. Range: -90 to 90.
longitude	number	Yes	Birth location longitude. Range: -180 to 180.
utc_offset_minutes	number	Yes	UTC offset in minutes (e.g., 330 for IST, -300 for EST).
ayanamsa	enum: kp \| kp_new \| lahiri \| raman \| true_chitra \| khullar	No	Ayanamsa system. Defaults to kp.
target_number	number	Yes	KP horary question number (1-249)
query_event	string	No	Event being queried (e.g., 'Marriage', 'Career / Job Start'). Triggers Moon connectivity check.
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": {
      "birth_datetime": "1992-08-14T04:32:00",
      "latitude": 6.927,
      "longitude": 79.861,
      "utc_offset_minutes": 330,
      "ayanamsa": "kp",
      "target_number": 137
    }
  }
}

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.