Advanced techniques

Varshesha, the Tajik Year Lord (A45) [Tajik]

get_varshesha

[Tajik] The year lord of one year of life by the stated rule (CLASSICAL-SOURCES A45), on its own. All five Panchadhikari are resolved and each is tested for a Tajik aspect to the annual ascendant; THE GATE COMES FIRST AND STRENGTH ONLY BREAKS TIES INSIDE IT: among several that aspect, the greatest panchavargeeya bala wins, and when none aspects the Muntha-pati is the fallback. Returns '{ frame: 'annual', annual: { targetYear, age, sunReturnDateUTC, chartLagnaSign, munthaSign }, yearLord, yearLordRationale, varshesha, yearLordLagnaLordOnly }'. 'yearLord' CAN BE NULL, which is an answer: 'varshesha.basis' is ASPECT_TEST, STRENGTH_TIE_BREAK, MUNTHA_PATI or UNDECIDED (an exact strength tie). 'varshesha.candidates' gives each candidate's 'role', 'planet', 'derivation', 'aspectsAnnualLagna' and 'aspectNote'; 'varshesha.aspecting' and 'varshesha.strengths' are what the tie-break compared, so the decision can be checked. The readings the sources leave open ship beside the primary, none chosen: the neutral rung ('yearLordNeutralAsFriend', 'neutralRungDecidesYearLord'), the tri-rashi tables ('triRashi', 'yearLordTriRashiMethodB', 'triRashiDecidesYearLord'), the gate's orb ('gateVariants', 'gateDecidesYearLord') and Narasimha Rao's whole chain ('narasimhaRaoChain'), all under 'varshesha'. 'yearLordLagnaLordOnly' is the annual lagna lord taken unconditionally, the figure returned before 2026-09-14. Call get_tajik_variant_spread for what the neutral rung moves on this chart. Nothing is scored. The same block 'get_varshaphala_chart' returns as 'varshesha', 'yearLord', 'yearLordRationale' and 'yearLordLagnaLordOnly', and 'get_tajik_yogas' under 'annual' with a 'target_year'.

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	The year of life whose birthday falls in this calendar year (default: current year).

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