Skip to main content
Glama
RoxyAPI

RoxyAPI Astrology MCP server

Official
by RoxyAPI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Solar Return Chart - Annual birthday forecast with relocated chart

post_astrology_solar_return
Read-only

Cast a solar return chart for any year to forecast your annual horoscope from your astrological birthday, with planets, houses, Ascendant, and aspects.

Instructions

Generate a solar return chart for any year, the foundational technique for annual astrological forecasting. The chart is cast for the exact moment the transiting Sun returns to its natal ecliptic longitude (your astrological birthday). Returns full tropical zodiac chart with planetary positions, house cusps, aspects, Ascendant, and Midheaven. Location-sensitive: relocating your solar return chart to a different city changes the houses and Ascendant. Solar return chart API, annual horoscope forecast, birthday chart calculator, yearly astrology prediction, relocated solar return.

Input Schema

NameRequiredDescriptionDefault
langNoResponse 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
compactNoSet 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.
latitudeYesLatitude of the solar return location in decimal degrees (-90 to 90). Use current residence or travel location at time of birthday. Solar return charts are location-sensitive.
timezoneYesDecimal hours from UTC OR IANA name (e.g. "America/New_York"). IANA resolved to the DST-correct offset for the birthDate. Output datetime is adjusted to this timezone.
birthDateYesOriginal birth date in YYYY-MM-DD format. Used to determine natal Sun longitude for the solar return calculation.
birthTimeYesOriginal birth time in 24-hour HH:MM:SS format. Determines exact natal Sun position for annual return timing.
longitudeYesLongitude of the solar return location in decimal degrees (-180 to 180). Affects house cusps and Ascendant of the return chart.
returnYearYesYear for which to cast the solar return chart. The chart is erected for the exact moment the transiting Sun conjuncts the natal Sun longitude in this year.
houseSystemNoHouse system for the solar return chart. Placidus (default) is most common in Western astrology. Whole Sign, Equal, and Koch also supported.placidus

Output Schema

NameRequiredDescriptionDefault
chartYes
locationYes
birthDateYes
interpretationYes
solarReturnDateYes
solarReturnYearYes
natalSunPositionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.2
    • changedInput schema / examples
      Previous value: -[
-  {
-    "birthDate": "1990-07-15",
-    "birthTime": "14:30:00",
-    "latitude": 40.7128,
-    "longitude": -74.006,
-    "returnYear": 2026,
-    "timezone": -5
-  }
-]New value: +[
+  {
+    "birthDate": "1990-07-15",
+    "birthTime": "14:30:00",
+    "latitude": 40.7128,
+    "longitude": -74.006,
+    "returnYear": 2026,
+    "timezone": "America/New_York"
+  }
+]
    • changedInput schema / properties / timezone / example
      Previous value: --5New value: +"America/New_York"
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful behavioral context (location sensitivity, the moment of casting) but, with an output schema present, its listing of returned fields is largely redundant and it omits rate limits or precision caveats.

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 core content is front-loaded and readable, but the closing string of SEO keywords ('Solar return chart API, annual horoscope forecast, birthday chart calculator, yearly astrology prediction, relocated solar return') is filler that adds no invocation value and dilutes the entry.

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, return values need not be spelled out, and the description nonetheless covers inputs, casting basis, and location sensitivity. It is nearly complete for an agent to call correctly, missing only explicit alternative-tool routing.

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 every parameter is already documented in the schema. The description's only added semantics is reinforcing that location inputs change houses/Ascendant, which the schema also states. Baseline 3 is appropriate.

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 (Generate) and resource (solar return chart) and precisely defines the technique: the chart cast for the moment the transiting Sun returns to its natal ecliptic longitude. This clearly distinguishes it from natal_chart, lunar_return, and planetary_returns siblings.

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?

It conveys the applicable scope ('for any year') and a key usage nuance ('Location-sensitive: relocating... changes the houses and Ascendant'), but never names when to choose this over siblings like post_astrology_lunar_return or post_astrology_planetary_returns, nor any prerequisites. Usage is implied 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.

Deploy Server

Other Tools