Advanced techniques

Lost Article: Will It Come Back, and When (KP horary)

get_lost_article_recovery

From the horary chart the question_number fixes: the 11th cusp sub lord against the recovery houses 2/6/11 and the loss houses 5/8/12 (KP Reader 6 page 235), its retrograde state read as KP reads motion ('recovery.retrogradeReading' carries the astronomical reading beside it, F160), the Moon in the lagna and a benefic in the 11th as confirmations; then the MD-AD-PD periods whose lords signify the recovery houses (page 245), in confidence order (an engine weighting). Returns '{ horaryAscendant, queryType, questionNumber, recovery: { verdict: PROMISED | DELAYED | NOT_RECOVERED | WITHHELD, eleventhCSL, eleventhCSLRetrograde, eleventhCSLSignifies, coversRecoveryHouses, coversLossHouses, moonInLagna, beneficInEleventh, rationale, summary, retrogradeReading }, recoveryDashaCandidates: [{ startDate, endDate, mahadasha, antardasha, pratyantardasha, recoveryHousesCovered, lossHousesCovered, confidence, pattern }], bookCitations, disclaimer, pagination, pageNote }'. **'recoveryDashaCandidates' is paged.** 'horaryAscendant', 'queryType' and 'questionNumber' echo the cast it read. The same fields 'get_lost_or_missing' returns as 'recovery' and 'recoveryDashaCandidates'. An aid to a search; for a theft or a missing person, the police come first. 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.
question_number	number	Yes	Querent's KP question number (1-249)
query_type	enum: theft \| lost \| missing_person	No	Type of horary query

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