Advanced techniques

Sub-Sub-Lord Boundary Sensitivity

get_subsub_boundary

Quantifies how close every house cusp and planet sits to a sub-sub-lord boundary (the 2,187-cell KCIL precision grid). Returns per-position arc-seconds to nearest boundary, the alternate sub-sub-lord that would apply if the position shifted across the boundary, and a CRITICAL/WARNING/STABLE flag. Includes a 0-100 twin-divergence index estimating how strongly this chart's KCIL-level predictions depend on birth-second precision. Use for birth-time precision audits, twin-chart analysis, and boundary-sensitive rectification.

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 \| lahiri \| raman \| true_chitra	No	Ayanamsa system. Defaults to kp.
threshold_arcsec	number	No	Critical-flag threshold in arc-seconds (default: 30).
include_planets	boolean	No	Include 9 planets in the analysis (default: true).
include_cusps	boolean	No	Include 12 house cusps (default: true).

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": "get_subsub_boundary",
    "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/subsub-boundary

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.