Advanced techniques

Surgery Success Outlook (KP)

get_surgery_success

Answers whether an operation will go WELL (get_medical_timing answers WHEN). Natal promise: 1st CSL must not signify 8/12 at L1 (vitality through the operation), 11th CSL on 1/5/11 (fulfilment), 8th CSL on 6/8/12 without 11 (complication-risk pattern), 6th CSL on 11 (disease removed), plus a natal Mars (surgeon's karaka) retrograde caution. Mars's combustion is reported and does not disqualify the karaka or move the score: KP reads the outcome from the 8th cusp sub lord's significations (F066, Q023 section 20). Returns successVerdict FAVOURABLE/GUARDED/UNFAVOURABLE, complicationRisks (Saturn prolonged recovery, Rahu/Ketu anaesthesia and unexpected findings, Mars bleeding tendency), recoverySpeedClass. With surgery_date it also grades the day itself: MD/AD/PD lords, transit Mars retrograde means DEFER (KP retrograde invalidation), ruling planets must carry a 1/5/11 significator, transit Moon star/sub hostility; dateVerdict GO/DEFER/RESCHEDULE with deferReasons and up to 3 recommendedWindows within 90 days when the date is not clean. Never replaces medical judgment, and emergency surgery is never delayed for astrology.

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.
surgery_date	string	No	ISO date or datetime of the planned operation. Presence switches to DATE_SPECIFIC mode. Without a timezone suffix it is read as local time at the birth location (date-only strings anchor at local noon).
surgery_type	enum: ELECTIVE \| EMERGENCY \| COSMETIC \| TRANSPLANT	No	Type of operation (default ELECTIVE). EMERGENCY prepends an explicit never-delay note to the disclaimer.

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_surgery_success",
    "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.