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/

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "asterwise_get_kp_ruling_planets"
  }
}

Input 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

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

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial non-obvious behavior: DST handling for skipped times (moved forward by the gap) and ambiguous times (first occurrence), plus data.local_time_status values. It also discloses the accepted date range (1800–2099) and which fields (target_utc, target_timezone) echo back what was used.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core purpose, then organizes the rest under labeled sections (WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE WITH), which is appropriate for a tool with real edge cases. It is long, but nearly every sentence carries distinct information; minor trimming of the DST detail is possible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, standalone vs. follow-up routing, the full input contract including defaults and DST edge cases, sibling disambiguation, and a doc link for the full output/error contract. With an output schema present, it does not need to enumerate return fields, and its brief mention of returned values is sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents lat/lon, date/time defaults, and timezone. The description nevertheless adds value beyond the schema: the 1800–2099 date-range constraint, the DST resolution rules, and the timezone default derivation from lat/lon. It does not add format/syntax beyond the schema, so it lands just above baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (computes), resource (KP ruling planets), and scope (at a lat/lon for the current instant or a given local date/time, with no birth data). It even names the returned components (day lord, Moon/Ascendant lord chains, deduplicated ruling_planets list). The DO NOT CONFUSE WITH block explicitly separates it from kp_chart and prashna_chart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit workflow routing: 'BEFORE: None — standalone. AFTER: asterwise_get_kp_chart — if natal confirmation is needed.' The DO NOT CONFUSE WITH section names the two nearest alternatives and the distinguishing condition for each (kp_chart needs BirthData; prashna_chart is horary). Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Asterwise tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?