Lal Kitab Chart

asterwise_get_lal_kitab_chart

Produces the Lal Kitab house and planet schema plus Rin (debt) flags from BirthData using Lal Kitab placement rules. Lal Kitab uses a distinct astrological system from standard Vedic computation, with its own house-based remedies.

Parameters

Parameter	Type	Required	Description
birth	object	yes	Birth data for a single person. Fields: date, time, lat, lon*, person_name, timezone, ayanamsa
response_format	enum: markdown, json	no

What it covers

Returns data.system 'lal_kitab', ayanamsa, planets{} with lk_house and pucca/kachcha flags, twelve houses{} with occupants and significations, and rin_analysis with boolean debts, active_rins[], and rin_remedies[] rows. Do not merge these houses with asterwise_get_natal_chart Bhava Chalit without explicit user intent — frameworks differ.

Workflow

BEFORE: None — standalone for Lal Kitab queries.
AFTER: asterwise_get_lal_kitab_remedies — practical totkas aligned to this chart.

Input

BirthData global contract; mixing interpretive systems in prose is a caller concern, not validated here.

Output contract

data.system (string — 'lal_kitab')
data.ayanamsa (string)
data.planets{} — Sun..Ketu:
longitude (float)
rashi_index (int)
rashi (string)
lk_house (int — 1–12)
house_lord (string)
is_retrograde (bool)
pucca_ghar (bool)
kachcha_ghar (bool)
uchcha (bool)
neecha (bool)
pucca_house (int)
kachcha_house (int)
data.houses{} — keys '1'..'12':
house (int)
rashi_index (int)
rashi (string)
lord (string)
occupants[] (string array)
signification (string)
has_benefic (bool)
has_malefic (bool)
data.rin_analysis:
pitru_rin, matru_rin, bhai_rin, stri_rin, dev_rin (bool)
active_rins[] (string array)
rin_remedies[] — { rin (string), planet (string), totka (string) }

Response format

response_format=json serialises the complete response as indented JSON — use this for programmatic parsing, typed clients, and downstream tool chaining. response_format=markdown renders the same data as a human-readable report. Both modes return identical underlying data — no fields are added, removed, or filtered by either mode.

Compute class

MEDIUM_COMPUTE

Errors

INVALID_PARAMS (local — caught before upstream call):
None — BirthData Pydantic only.

INVALID_PARAMS (upstream):
— None — upstream rejection surfaces as MCP INTERNAL_ERROR at the tool layer.

INTERNAL_ERROR:
— Any upstream API failure or timeout → MCP INTERNAL_ERROR

Edge cases:
— Lal Kitab houses are not interchangeable with cusps.

Do not confuse with

asterwise_get_natal_chart — classical radix, not Lal Kitab lk_house logic.
asterwise_get_lal_kitab_remedies — remedy list without full chart geometry.

Connect

Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.