KP Ruling Planets
asterwise_get_kp_ruling_planets
Computes KP ruling planets for the instantaneous chart at lat/lon with no birth data and returns day lord, Moon/Ascendant lord chains, and a deduplicated ruling_planets list.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
lat | number | yes | Latitude in decimal degrees, north positive (e.g. 13.08). |
lon | number | yes | Longitude in decimal degrees, east positive (e.g. 80.27). |
response_format | enum: markdown, json | no | Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload. |
What it covers
Current-moment KP snapshot: target_utc, day_lord, Moon and Ascendant tuples with sign/nakshatra/sub lords, ruling_planets[] unique names. Not natal positions (asterwise_get_kp_chart) and not house significators (asterwise_get_kp_significators). Coordinate sanity is upstream — not locally validated floats beyond whatever FastMCP passes.
Workflow
BEFORE: None — this tool is standalone.
AFTER: asterwise_get_kp_chart — if natal confirmation is needed afterwards.
Input
lat and lon only; no date parameter — "now" is implicit on the server clock.
Output contract
data.ayanamsa (string — 'kp')
data.target_utc (string — ISO UTC)
data.day_lord (string — planet name)
data.moon:
longitude (float)
rashi (string)
sign_lord (string)
nakshatra_lord (string)
sub_lord (string)
data.ascendant — same fields as data.moon
data.ruling_planets[] (string array — unique names, deduplicated)
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
FAST_LOOKUP
Errors
INVALID_PARAMS (local — caught before upstream call):
None — lat/lon not range-checked locally.
INVALID_PARAMS (upstream):
— None — coordinate errors surface as MCP INTERNAL_ERROR at the tool layer.
INTERNAL_ERROR:
— Any upstream API failure or timeout → MCP INTERNAL_ERROR
Edge cases:
— Represents instantaneous sky — differs from natal stored charts.
Do not confuse with
asterwise_get_kp_chart — needs BirthData and returns full natal KP cusps.
asterwise_get_prashna_chart — horary keyword workflow, not ruling-planet snapshot.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.