Core analysis

Full KP Birth Chart

get_full_chart

The opening layer of a KP birth chart, in one call. Returns '{ planets[9], houses[12], currentDasha, rulingPlanets, detail }'. Each planet carries sign, house, degree, sign/star/sub lord, retrograde and combust; each house its sign and three lords; 'currentDasha' names the running MD, AD and PD WITHOUT their subtrees. Use when: you need an overview or are starting any reading. **This is deliberately not everything the engine computed, and the 'detail' block in the response names the tool holding each deeper layer**: 'get_planets' for sub-sub lord, KP number, nakshatra, pada and dignity, 'get_house_cusps' for cusp longitudes, 'get_significators' for the 4-level matrix, 'get_dasha_periods' and 'get_pratyantardasha_periods' for the dasha tree, 'get_boundary_warnings' for sub lord credibility. Call those rather than assuming this covered them. The significator matrix in particular is NOT repeated here, because it is byte for byte what get_significators returns and the protocol calls that tool anyway.

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.

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