Specialized analysis

RP Chart Verification

get_rp_chart_verification

A check on the birth time: whether the Ascendant's sign lord, star lord and sub lord are among the ruling planets of the birth moment. 'verification_score' is how many of the three are (0 to 3); 'verdict' is CONFIRMED (star and sub) / LIKELY_ACCURATE / UNCERTAIN / UNCONFIRMED. Returns '{ ascendant_longitude, ascendant_sign, ascendant_sign_lord, ascendant_star_lord, ascendant_sub_lord, rps_at_birth, sign_lord_in_rps, star_lord_in_rps, sub_lord_in_rps, verification_score, verdict, confidence, notes }'. For a fuller rectification use 'rectify_by_event_ruling_planets'. The same block 'get_profession_indicators' returns as 'ruling_planet_applications.chart_verification'.

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.

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

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.