Asterwise

KP Ruling Planets

asterwise_get_kp_ruling_planets

Read-onlyIdempotent

Computes KP ruling planets at a latitude and longitude for the current instant or a given local date and time, with no birth data. Returns the day lord, Moon and Ascendant lord chains, and a deduplicated ruling_planets list.

WORKFLOW: BEFORE: None — this tool is standalone. AFTER: asterwise_get_kp_chart — if natal confirmation is needed afterwards.

INPUT CONTRACT: lat and lon required. Optional target_date (YYYY-MM-DD), target_time (HH:MM), target_timezone (IANA; defaults to the zone at lat/lon). With neither date nor time the server uses the current instant (KP judges ruling planets at the moment of judgment); time only = that time today; date only = 12:00 local. data.target_utc and data.target_timezone show what was used. target_date must be within 1800-01-01 to 2099-12-31. A time skipped by a daylight-saving change is read with the offset before the change (moved forward by the gap); a time that occurred twice is read as the first occurrence; data.local_time_status is 'nonexistent' / 'ambiguous' / 'ok'.

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.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-kp-ruling-planets/

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lat`	Yes	Latitude in decimal degrees, north positive (e.g. 13.08).
`lon`	Yes	Longitude in decimal degrees, east positive (e.g. 80.27).
`target_date`	No	Local date of the moment to judge, YYYY-MM-DD. Without target_time, 12:00 local is used. Omit both date and time for the current instant.
`target_time`	No	Local time of the moment to judge, HH:MM (24-hour). Without target_date, that time today. Omit both date and time for the current instant.
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown
`target_timezone`	No	IANA time zone for target_date and target_time, e.g. 'Asia/Kolkata'. Defaults to the zone at lat/lon.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 8, 2026

addedInput schema / properties / target_date

Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Local date of the moment to judge, YYYY-MM-DD. Without target_time, 12:00 local is used. Omit both date and time for the current instant."
+}

addedInput schema / properties / target_time

Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^\\d{2}:\\d{2}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Local time of the moment to judge, HH:MM (24-hour). Without target_date, that time today. Omit both date and time for the current instant."
+}

addedInput schema / properties / target_timezone

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "IANA time zone for target_date and target_time, e.g. 'Asia/Kolkata'. Defaults to the zone at lat/lon."
+}

Changed3 schema fields changedSep 5, 2026

addedInput schema / properties / lat / description

Added value: +"Latitude in decimal degrees, north positive (e.g. 13.08)."

addedInput schema / properties / lon / description

Added value: +"Longitude in decimal degrees, east positive (e.g. 80.27)."

addedInput schema / properties / response_format / description

Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."

Changed2 schema fields changedSep 4, 2026

addedInput schema / properties / response_format / default
```
Added value: +"markdown"
```

changedInput schema / required

Previous value: -[
-  "lat",
-  "lon",
-  "response_format"
-]New value: +[
+  "lat",
+  "lon"
+]

First observedApr 22, 2026

TDQS

Score is being calculated.

All Asterwise tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?