Specialized analysis

Birth Time Rectification

rectify_birth_time

Refine an uncertain birth time by testing ±30 min around the stated time against known life events. Requires at least 1 known event with date and houses that should have been active. Returns '{ candidates: [{ datetime, score, eventMatches[] }], bestCandidate, originalTime, refinedTime }'. For RP-confirmation rectification using event location (more rigorous) use 'get_rectification_advanced'. For finding entirely-unknown birth time use 'find_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 \| kp_new \| lahiri \| raman \| true_chitra \| khullar	No	Ayanamsa system. Defaults to kp.
known_events	array<object>	Yes	Known life events with dates and relevant houses
range_minutes	number	No	Search range in minutes. Default: 30
step_minutes	number	No	Step size in minutes. Default: 2

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": "rectify_birth_time",
    "arguments": {
      "birth_datetime": "1992-08-14T04:32:00",
      "latitude": 6.927,
      "longitude": 79.861,
      "utc_offset_minutes": 330,
      "ayanamsa": "kp",
      "known_events": []
    }
  }
}

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.