Advanced techniques

Advanced Horary Analysis

get_horary_advanced

Advanced horary analysis: number intuition analysis (checks if chosen KP number's sub-lord independently signifies query houses, classifying it as self-confirmatory vs weakly chosen) and horary-natal cross-validation (compares fruitful significators between both charts: convergence means highest confidence prediction, divergence means suspect birth time).

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 \| lahiri \| raman \| true_chitra	No	Ayanamsa system. Defaults to kp.
target_number	number	Yes	KP horary question number
query_event	string	Yes	The event or question being queried. Use a short keyword or phrase (e.g., 'Marriage', 'Job offer', 'Foreign travel', 'Health recovery', 'Property purchase', 'Exam result').

Example call

Send the request as a standard MCP tools/call:

POST https://mcp.lumin.guru/mcp
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_horary_advanced",
    "arguments": {
      "birth_datetime": "1992-08-14T04:32:00",
      "latitude": 6.927,
      "longitude": 79.861,
      "utc_offset_minutes": 330,
      "ayanamsa": "kp",
      "target_number": 137,
      "query_event": "..."
    }
  }
}

Engine endpoint

This tool delegates to the kp-engine endpoint:

POST /v1/kp/horary/advanced

The engine is a private internal service. All public access flows through the MCP server, which handles auth, rate limiting, and response compaction.

Birth data

This tool requires birth data. If you have already called set_birth_profile in the same conversation, the MCP server injects those fields automatically and you can omit them from the call.