Advanced techniques
Lost Article / Theft / Missing-Person Horary (KP)
get_lost_or_missing
KP horary direction-finding for lost articles, theft, and missing persons. Takes a question_number (1-249) and a query_type ('theft' | 'lost' | 'missing_person'). Returns cardinal direction (E/W/N/S, derived from a planet in Kendhra or lagna fallback), distance class (SAME_PLACE / NEAR / MODERATE / FAR / ABROAD, from 7th significator's sub-lord house), in-house location (gate / middle / backyard, from lagna drekkana), recovery verdict (PROMISED / DELAYED / NOT_RECOVERED / WITHHELD), recovery dasha candidates, and a thief description with stature, age, sex, colour, shape, and whether the thief is a known relative, stranger, or neighbour. All rules grounded in KP Reader VI Slokas 1-4, 47, 49-59 and pages 50, 51, 64, 235, 237, 245. Investigative lens; not a substitute for police investigation in theft or missing-person cases. The 11th CSL's retrograde test reads motion as KP does, Rahu and Ketu never (Reader 6 canon p.114); 'recovery.retrogradeReading' carries the astronomical reading and its verdict beside it (F160). Each claim is also a tool of its own, named in 'methodSeams' and casting the same chart: 'get_lost_article_recovery' (paged), 'get_lost_article_location', 'get_lost_article_nature' and 'get_lost_article_thief'. Call those when a reading needs one; this tool returns every part in one call. 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:
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_or_missing",
"arguments": {
"judgement_datetime": "2026-10-20T10:30:00",
"judgement_latitude": 6.927,
"judgement_longitude": 79.861,
"judgement_time_zone": "Asia/Colombo",
"question_number": 0
}
}
}