RoxyAPI Astrology MCP server

Official

by RoxyAPI

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Calculate planetary transits - Current transits with natal chart comparison

post_astrology_transits

Read-only

Calculate current or future planetary transits, then compare them with a natal chart to find transit-to-natal aspects, signs, degrees, speeds, orbs, and applying/separating status.

Instructions

Calculate current or future planetary transits (positions of all bodies now). Optionally compare transits to natal chart to find transit-to-natal aspects. Returns all 14 celestial bodies (the 10 classical planets, the lunar nodes, Chiron, and Black Moon Lilith) with signs, degrees, and speeds. When natal chart provided, includes transit aspects (transiting Sun conjunct natal Mars, etc.) with orbs and applying/separating status. Perfect for daily transit forecasts, aspect alerts, and personalized transit reports.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Transit date in YYYY-MM-DD format (defaults to current date)
`lang`	No	Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English.	en
`time`	No	Transit time in HH:MM:SS format (defaults to current time)
`compact`	No	Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
`nodeType`	No	Lunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass "mean" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to "true".	true
`timezone`	No	Transit timezone: decimal hours from UTC OR IANA name (e.g. "America/New_York"). IANA resolved to the DST-correct offset for the transit date. Defaults to 0 (UTC).
`natalChart`	No	Optional natal chart data to compare transits against

Output Schema

TableJSON Schema

Name	Required	Description	Default
`summary`	No
`timezone`	Yes
`transitDate`	Yes
`transitTime`	Yes
`transitAspects`	No
`transitPlanets`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish a safe read-only, non-destructive operation, so the bar is lower. The description still adds real value by disclosing what is returned: all 14 bodies with signs/degrees/speeds, plus transit aspects with orbs and applying/separating status. No auth, rate-limit, or error behavior is mentioned, which would have pushed this higher.

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?

Four sentences, front-loaded with the core operation before the optional mode and the return contents. Informative without being padded, though the final 'Perfect for...' sentence is promotional rather than operational.

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?

For a 7-parameter tool with a nested object, rich enums, and an output schema, the description covers the operation, the optional branch, and the shape of results adequately. It omits any mention of the date-range limits or error codes present in the schema, but those live in the structured fields.

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 100%, so the schema already carries the parameter burden; the description does not add syntax or format detail beyond it. It does clarify the behavioral effect of supplying natalChart (adds transit-to-natal aspects), a marginal gain over the schema's own 'Optional natal chart data to compare transits against'.

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+resource (calculate planetary transits) with scope (current/future), and explicitly describes the optional natal-chart comparison mode. This distinguishes it from siblings like post_astrology_transit_aspects and post_astrology_transits_monthly, which cover narrower or period-based variants.

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

Usage Guidelines4/5

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

Gives clear use context ('Perfect for daily transit forecasts, aspect alerts, and personalized transit reports') and states the conditional mode (provide natalChart to get transit-to-natal aspects). It does not, however, explicitly name when to prefer post_astrology_transit_aspects or post_astrology_transits_monthly instead.

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

Deploy Server