Planetary Hours
asterwise_get_western_planetary_hours
The 24 planetary hours for a date and place, with the planet ruling each hour and local plus UTC start and end times. Day (sunrise to sunset) and night (sunset to next sunrise) are each split into 12 equal parts; the first hour after sunrise belongs to the weekday's planet and the rest follow the Chaldean order (Saturn, Jupiter, Mars, Sun, Venus, Mercury, Moon).
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
location | object | yes | For tools that need location but not birth time. Required fields: date, lat, lon. Optional fields: timezone, response_format. |
What it covers
Western planetary hours (same maths as asterwise_get_hora, Western naming, ISO times in both local time and UTC). No birth data needed.
Workflow
BEFORE: None — standalone.
AFTER: asterwise_get_western_void_of_course_moon — avoid void-of-course windows.
Input
location — LocationInput (date YYYY-MM-DD, lat, lon, timezone, response_format).
Output contract
data.date, data.weekday, data.day_ruler, data.convention
data.sunrise_local, data.sunset_local, data.next_sunrise_local (+ *_utc twins)
data.day_hour_minutes, data.night_hour_minutes
data.hours[] — hour (1–24), period (day|night), planet, start_local, end_local, start_utc, end_utc, length_minutes, is_current
Response format
response_format=json — structured hours. response_format=markdown — readable table.
Compute class
FAST_LOOKUP
Errors
INVALID_PARAMS (local): LocationInput validation failures.
INVALID_PARAMS (upstream): polar day/night with no sunrise → 422, surfaces as MCP INTERNAL_ERROR with the API message.
INTERNAL_ERROR: Any upstream API failure → MCP INTERNAL_ERROR
Do not confuse with
asterwise_get_hora — the Vedic version with Sanskrit framing and activity notes.
asterwise_get_choghadiya — 8 Vedic day/night parts, not 12.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.