Skip to main content

Prashna Chart

asterwise_get_prashna_chart

Casts a Prashna chart for the query instant from the supplied date, time, place and a single-topic keyword. Returns houses, Moon diagnostics, a verdict, and cusps.

Parameters​

ParameterTypeRequiredDescription
prashnaobjectyesPrashna (horary) query parameters. Required fields: question, date, time, lat, lon. Optional fields: timezone, ayanamsa, response_format.

What it covers​

Horary workflow: maps one of the approved keywords to a primary house (the house and its lord are whole sign from the Prashna lagna; data.house_cusps lists the quadrant cusps and the lords of their signs, which can differ), evaluates Moon (phase, VOC, affliction), applies Tajika Ithasala/Musaripha between the Lagna lord and the quesited house lord (sign aspects 1/3/4/5/7/9/10/11, faster planet by mean motion, mean-Deeptamsa orb; both false when one planet rules both houses, e.g. 'self'), aggregates graha dignities/houses from Prashna Lagna, and emits verdict/confidence/score. Not natal life analysis (asterwise_get_natal_chart) and not KP cusps from birth (asterwise_get_kp_chart).

Workflow​

BEFORE: None — standalone for horary.
AFTER: None.

Input​

question must be exactly one of: self, wealth, siblings, property, children, health, marriage, death, travel, career, gains, loss. Full sentences are not validated locally and are rejected upstream → MCP INTERNAL_ERROR at the tool layer. PrashnaInput enforces date/time/lat/lon/ayanamsa patterns locally.

Output contract​

data.ayanamsa (string)
data.question (string — keyword echoed)
data.primary_house (int)
data.ithsala_applying (bool — Tajika Ithasala; false when one planet rules both houses)
data.ithsala_separating (bool — Tajika Musaripha)
data.query_utc (string — ISO UTC)
data.lagna:
rashi_index (int)
rashi (string)
longitude (float)
lord (string)
data.house_analysis:
house (int)
rashi_index (int)
rashi (string)
lord (string)
lord_dignity (string)
lord_house (int)
lord_longitude (float)
occupants[] (string array)
data.moon:
longitude (float)
rashi_index (int)
rashi (string)
nakshatra (string)
phase (string — 'waxing' or 'waning')
dignity (string)
void_of_course (bool)
afflicted_moon (bool)
applying_to_benefic (bool)
data.verdict:
verdict (string — 'favorable', 'mixed', or 'unfavorable')
confidence (string — 'high', 'medium', or 'low')
score (int — negative unfavorable, positive favorable)
data.planets{} — per planet: longitude (float), rashi_index (int), rashi (string), house (int), is_retrograde (bool), dignity (string)
data.house_cusps{} — keys '1'..'12': rashi_index (int), rashi (string), lord (string), longitude (float)

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):
— PrashnaInput Pydantic violations (date, time, lat, lon, ayanamsa) → MCP INVALID_PARAMS

INVALID_PARAMS (upstream):
— None — bad question tokens surface as MCP INTERNAL_ERROR at the tool layer.

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

Edge cases:
— Moon void-of-course flagged classically negative for outcomes.

Do not confuse with​

asterwise_get_natal_chart — requires birth data, not query-moment prashna.
asterwise_get_kp_chart — natal KP from birth time, not horary keyword mapping.

Connect​

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