Skip to content
Lumindocs
UseBuildChangelog
Open Lumin
All tools

Core analysis

Natal Promise Analysis

analyze_natal_promise

Run Cuspal Sub Lord (CSL) promise analysis across 25 life events. The CSL is the planet ruling the sub-division at a house cusp, KP's deciding factor for whether any event is promised in the chart. Returns '{ events: { Marriage, Career, Childbirth, Foreign Travel, ... }: { verdict: PROMISED|DENIED|MIXED_ACTIVE, coveragePct, supportingHouses[], detrimentalHouses[], cslChain } }'. Use when: starting any life-event question, call this BEFORE timing tools.

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 | lahiri | raman | true_chitraNoAyanamsa system. Defaults to kp.

Example call

Send the request as a standard MCP tools/call:

http
POST https://mcp.lumin.guru/mcp
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "analyze_natal_promise",
    "arguments": {
      "birth_datetime": "1992-08-14T04:32:00",
      "latitude": 6.927,
      "longitude": 79.861,
      "utc_offset_minutes": 330,
      "ayanamsa": "kp"
    }
  }
}

Engine endpoint

This tool delegates to the kp-engine endpoint:

http
POST /v1/kp/csl-analysis

The engine is a private internal service. All public access flows through the MCP server, which handles auth, rate limiting, and response compaction.

Birth data

This tool requires birth data. If you have already called set_birth_profile in the same conversation, the MCP server injects those fields automatically and you can omit them from the call.