Advanced techniques

Harsha Bala, Tajik's Four Situations of Joy (A44) [Tajik]

get_harsha_bala

[Tajik] Harsha bala on its own (CLASSICAL-SOURCES A44): four binary situations per planet, five points each, sthana (the house of joy), uccha-swakshetra (exaltation or own sign), stri-purusha (gender in a gendered house or sign) and diva-ratri (day or night return). Returns '{ frame: 'natal' | 'annual', annual?: { targetYear, age, sunReturnDateUTC, chartLagnaSign }, harsha: [{ planet, components: [{ component, points, computed, reason, source }], points, reachableTotal, genderTestVariant: { reading, onSign, onHouse, source }, statedTotal, notComputed }], gaps, methodNote, houseConvention, pagination, pageNote }'. **'points' is out of 'reachableTotal', not out of 20**: on the natal frame there is no solar return to be day or night, so diva-ratri does not run and each planet reaches 15; pass 'target_year' for that year's solar-return chart and all four run. The gender test is applied to the SIGN by A44 and to the HOUSE by Q034, so 'genderTestVariant' carries both answers, neither resolved. The planetary genders are the TAJIK ones, where Mercury and Saturn are female and BPHS treats both as neuter. 'gaps' lists what both Tajik strength systems leave open, each line prefixed with its system. Nothing is ranked. **'harsha' is paged by planet.** The same block 'get_tajik_yogas' returns as 'bala.harsha'.

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.
target_year	number	No	Score the planets on that year's solar-return (annual) chart, where all four situations run. Omit for the natal chart, where diva-ratri cannot.

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