Skip to content
docs
UseBuildChangelog
Open Lumin
All tools

Specialized analysis

Yoga Detection

detect_yogas

[Vedic Parashari] Detect classical planetary yogas, special combinations producing distinctive life patterns. Includes Raja Yoga (a kendra lord and a trikona lord by whole-sign lordship in exchange, in one sign, or in mutual full aspect, BPHS 34.11-12 and 39.33-38, one row per pair; pairs 34.15 cancels are listed in 'rajaYogaPairs'; Yogakaraka rows per 34.13), Dhana Yoga (the 2nd and 11th lords per BPHS 13.4-5 by the Sanskrit, with Santhanam's English reading in 'variantReadings'; the 41.16 givers of wealth, the 5th and 9th lords, in 'dhanaGivers'), Gajakesari in BOTH its BPHS recensions, labelled and neither picked (Jupiter in a kendra from the lagna or the Moon with a benefic and not debilitated, combust or in an enemy's sign, 36.3; and the Moon-only form), Lakshmi (the 9th lord in a kendra in its own, moolatrikona or exaltation sign, 36.27; the lagna lord's strength is not evaluated and the row says so), Budh-Aditya (Sun and Mercury in one sign → intellect; Mercury's combustion is reported, not applied), Pancha Mahapurusha (5 'great person' configurations, one row per qualifying planet), Saraswati, Amala, Vish, Chatursagara. Every lordship row carries 'source'. The rules these four used before 2026-09-28 (Placidus occupancy and degree orbs) ship uncounted in 'legacyRows', labelled unsourced, and 'corpusPosition' records that KP Reader 3 rejects these yogas as a method. Returns '{ yogas: [{ name, category, present, strength, formingPlanets[], description, effects, source? }], totalPresent, beneficYogas, maleficYogas, rajaYogaPairs, dhanaGivers, legacyRows, corpusPosition }'. For Vipreet/Neecha-Bhanga/Adhi/Lunar/Chandra-Mangal yogas, use 'detect_raja_and_lunar_yogas'. For Sun yogas (Vasi/Vesi/Ubhayachari) use 'get_sun_yogas'.

Parameters

NameTypeRequiredDescription
birth_datetimestringYesBirth date and time in ISO 8601 format (e.g., "1990-05-15T14:30:00").
latitudenumberYesBirth location latitude. Range: -90 to 90.
longitudenumberYesBirth location longitude. Range: -180 to 180.
utc_offset_minutesnumberYesUTC offset in minutes (e.g., 330 for IST, -300 for EST).
ayanamsaenum: kp | kp_new | lahiri | raman | true_chitra | khullarNoAyanamsa 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": "detect_yogas",
    "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.