RoxyAPI Astrology MCP server

Official

by RoxyAPI

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Secondary progressions calculator - progressed chart, progressed Sun and Moon

post_astrology_progressions

Read-only

Generate a secondary progressed chart for any date using the day-for-a-year key. Returns progressed planets, signs, houses, Ascendant, Midheaven, and Sun/Moon timing markers.

Instructions

Generate the secondary progressed chart for any date using the day-for-a-year key. Each day of ephemeris motion after birth stands in for one year of life. Returns every progressed body with its sign, degree, whole-sign house, motion, and retrograde state, plus the progressed Ascendant and Midheaven via the Naibod arc. The progressed Sun and progressed Moon are the headline timing markers for inner growth and emotional chapters. Secondary progressions API, progressed chart calculator, progressed Sun and Moon, progressed Ascendant and Midheaven.

Input Schema

Name	Required	Description	Default
`date`	Yes	Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.
`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`	Yes	Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.
`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.
`latitude`	Yes	Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.
`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`	Yes	Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time.
`longitude`	Yes	Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.
`targetDate`	Yes	Date to progress the chart to, in YYYY-MM-DD format. Usually today or a forecast date. The day-for-a-year key turns the elapsed years since birth into the same number of ephemeris days after the birth moment.

Output Schema

Name	Required	Description	Default
`planets`	Yes
`summary`	Yes
`ascendant`	Yes
`midheaven`	Yes
`targetDate`	Yes
`birthDetails`	Yes
`elapsedYears`	Yes
`progressedDate`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.1.2Oct 5, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "date": "1990-07-15",
-    "latitude": 40.7128,
-    "longitude": -74.006,
-    "targetDate": "2025-07-15",
-    "time": "14:30:00",
-    "timezone": -5
-  }
-]New value: +[
+  {
+    "date": "1990-07-15",
+    "latitude": 40.7128,
+    "longitude": -74.006,
+    "targetDate": "2025-07-15",
+    "time": "14:30:00",
+    "timezone": "America/New_York"
+  }
+]

changedInput schema / properties / timezone / example

Previous value: --5New value: +"America/New_York"

First observedv0.1.0Oct 4, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already establish the safe read-only profile. The description adds the calculation method and the returned contents (bodies with sign, degree, whole-sign house, motion, retrograde state, plus Ascendant/Midheaven via the Naibod arc), which is useful, but it says nothing about limits, accuracy caveats, or behavior when the birth time is unknown.

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

Conciseness3/5

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

The opening is well front-loaded and technically informative, but the trailing sentence ('Secondary progressions API, progressed chart calculator, progressed Sun and Moon, progressed Ascendant and Midheaven') is pure keyword stuffing that repeats earlier content and dilutes the definition.

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 need not enumerate return fields, yet it usefully summarizes them, and annotations cover safety. For a 9-parameter tool it is largely complete; only the missing routing guidance against sibling techniques keeps it from a 5.

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 coverage is 100% and the schema already explains every parameter, including the day-for-a-year semantics of targetDate. The description restates that mechanism at a high level but adds no format, default, or edge-case detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb (generate) and resource (secondary progressed chart) and explains the defining technique, the day-for-a-year key, which implicitly separates it from solar arc and profections. However, it never names a sibling tool, so the differentiation is inferential rather than explicit.

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?

The description explains what progressions are and that the progressed Sun/Moon are timing markers, but gives no when-to-use guidance, no conditions for choosing this over transits, profections, or solar arc, and no prerequisites or exclusions.

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

Deploy Server