Skip to main content
Glama
astroway

astroway-mcp

Official
by astroway

Planetary Hours

astroway_calendar_planetary_hours
Read-onlyIdempotent

Calculates Chaldean planetary hours for a date and location, returning 12 daytime and 12 nighttime hours; pass a local time to mark the current hour.

Instructions

Chaldean planetary hours for a date and place: 12 from sunrise to sunset and 12 from sunset to sunrise, so an hour is rarely 60 minutes. startHour and endHour are decimal local hours. Send atLocalHour (decimal local time, e.g. 15.2 for 15:12) to have the hour containing it marked isCurrent; without it no hour carries the field, because the answer is cacheable and a flag from the server clock would be stale by the time it renders.

[Group: Calendar & Cycles] [Endpoint: POST /v1/planetary-hours] [Required: date, latitude, longitude] [Cost: 10 credits (Tier 1)]

Input Schema

NameRequiredDescriptionDefault
dateYes
latitudeYes
timezoneNoIANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
longitudeYes
atLocalHourNoLocal time of day in decimal hours, e.g. 15.2 for 15:12. When sent, the hour containing it carries isCurrent: true and every other hour carries false. When omitted, no hour carries the field at all: it is not false, it is unasked.
timezoneOffsetNoHours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

Output Schema

NameRequiredDescriptionDefault
dateNo
hoursNo
latitudeNo
sunTimesNo
timezoneNo
dayOfWeekNo
longitudeNo
dayRulerPlanetIdNo
dayRulerPlanetNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: the 12+12 unequal-hour model, the decimal local-hour representation, and the caching rationale for why isCurrent is omitted unless requested.

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?

The description is front-loaded with the core concept and uses only two substantive sentences. The explanatory clause about caching earns its place, though the embedded endpoint and cost metadata add some surrounding noise.

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

Completeness3/5

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

The description covers the calculation and the isCurrent behavior, and an output schema exists so return values do not need full explanation. Still, for a tool in a crowded family with similar planetary-hour siblings, the lack of selection guidance leaves an important contextual gap.

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

Parameters3/5

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

Schema description coverage is 50%, and the description adds useful meaning for atLocalHour, startHour, and endHour. However, it does not compensate for the undocumented required parameters date, latitude, and longitude beyond what their names imply, nor does it discuss timezone and timezoneOffset.

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

Purpose4/5

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

The description clearly states the specific resource and calculation: Chaldean planetary hours for a date and place, divided into 12 daylight and 12 nighttime hours. It explains the non-standard hour length, but does not explicitly distinguish this tool from similar siblings such as astroway_horary_planetary_hours.

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

Usage Guidelines2/5

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

It offers no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The only conditional guidance concerns atLocalHour, not tool selection.

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

Deploy Server

Other Tools