Advanced techniques

Serial Horary Trend Across Multiple Sessions (KP T22)

get_horary_serial

For an ongoing situation (court case, prolonged job search, long illness), the practitioner casts horary charts at intervals and tracks how the CSL signification evolves. Pass at least 2 session moments and a topic; the engine casts each session's chart with the Ascendant fixed by that session's number at the commencement of its sub (KP Reader 6), runs the topic CSL verdict, and emits per-session snapshots (verdict, coverage_pct, supporting/detrimental houses, the fixed horary Ascendant and its sub lord, delta vs previous). Trend mapping: OSCILLATING, RESOLUTION_NEAR (coverage trending up, verdict improving), WORSENING (coverage falling, new detrimental houses), STABLE_FAVORABLE, or STABLE_UNFAVORABLE. No birth data: each session is cast at the moment and place that session's question is judged, sent on the session as 'judgement_datetime' (the local wall clock there), 'judgement_latitude', 'judgement_longitude', and 'judgement_utc_offset_minutes' or 'judgement_time_zone'. Snapshots come back in time order, each echoing its 'horaryMoment' ('instant', 'local', 'place', 'source', 'utcOffsetSource', 'timeZone'); 'deprecatedInput' names any old field name a session used and the field to send instead.

Parameters

Name	Type	Required	Description
sessions	array<object>	Yes	At least 2 sessions, each judged at its own moment and place with its own number.
topic	string	Yes	Event being tracked across sessions (uses the standard 4-level fuzzy event lookup)
ayanamsa	enum: kp \| lahiri \| raman \| true_chitra	No	Default: kp

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_serial",
    "arguments": {
      "sessions": [],
      "topic": "..."
    }
  }
}