AstroWay Core astrology

Planetary Hours

astroway_calendar_planetary_hours

Read-onlyIdempotent

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

Name	Required	Description
`date`	Yes
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`latitude`	Yes
`timezone`	No	IANA 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.
`longitude`	Yes
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`atLocalHour`	No	Local 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.
`timezoneOffset`	No	Hours 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

Name	Required	Description	Default
`date`	No
`hours`	No
`latitude`	No
`sunTimes`	No
`timezone`	No
`dayOfWeek`	No
`longitude`	No
`dayRulerPlanetId`	No
`dayRulerPlanetName`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, and non-destructive traits, so the bar is lower. The description still adds real context: the caching rationale for omitting isCurrent, and the precise 'not false, it is unasked' semantics, which the agent could not infer from annotations alone.

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 purpose and the hour-count rule are front-loaded, and the atLocalHour rationale follows economically. The metadata block (group, endpoint, required, cost) is boilerplate but compact; there is no rambling.

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

Completeness4/5

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

With an output schema present, the description needn't document return values, and it correctly names startHour/endHour/isCurrent. Combined with annotations and the schema's timezone/timezoneOffset docs, an agent has enough to call this correctly, though no cross-tool routing is offered.

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 63%, with strong per-parameter docs for timezone, timezoneOffset, precision, and atLocalHour. The description largely restates the atLocalHour schema text and only adds the output-side names startHour/endHour, so it meets but does not exceed the baseline for partially documented params.

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 resource and computation: Chaldean planetary hours for a date and place, with the defining rule that hours are 12 sunrise-to-sunset and 12 sunset-to-sunrise and are rarely 60 minutes. That framing clearly separates it from siblings like planetary_phases and planetary_cycles.

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

Usage Guidelines3/5

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

The description gives clear conditional guidance for atLocalHour (send it to get isCurrent, omit it for cacheable results), but never says when to choose this tool over siblings such as sun_times or lunar_calendar. Usage is implied by the topic rather than explicitly routed.

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

All AstroWay Core astrology tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?