Western Astrology MCP Server by RoxyAPI

Monthly Transits - Tropical sign ingresses for an entire month

post_astrology_transits_monthly

Read-only

Get every tropical sign change for a given month, for all 14 Western bodies: the Sun through Pluto, both lunar nodes, Chiron and Black Moon Lilith. Returns the starting sign of each body on the first of the month and then each ingress with its exact date and time in your timezone. Omit year and month to get the month in progress, so a published transit calendar stays current without a redeploy. Essential for transit calendars, monthly forecast copy, retrograde and ingress tracking, and newsletter automation. Monthly transit API, planetary ingress calendar, sign change dates, tropical transit table. Verified against NASA JPL Horizons, with the four cardinal ingresses cross-checked against published equinox and solstice times.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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
`year`	No	Year for the monthly transit table (1900-2100). Defaults to the current year (UTC).
`month`	No	Month number (1-12). Defaults to the current month (UTC).
`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	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 once, at the start of the window, and that offset applies to every time in the response. Ingress dates and times are reported in this zone, which is what makes a published calendar read correctly for its audience. Defaults to 0 (UTC).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`year`	Yes
`month`	Yes
`timezone`	Yes
`transitEvents`	Yes
`startingPositions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 23, 2026

changedInput schema / properties / timezone / description

Previous value: -"Timezone offset from UTC in hours. Ingress dates and times are reported in this zone, which is what makes a published calendar read correctly for its audience. Defaults to 0 (UTC)."New value: +"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 once, at the start of the window, and that offset applies to every time in the response. Ingress dates and times are reported in this zone, which is what makes a published calendar read correctly for its audience. Defaults to 0 (UTC)."

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "month": {
+      "type": "number"
+    },
+    "startingPositions": {
+      "items": {
+        "properties": {
+          "longitude": {
+            "type": "number"
+          },
+          "planet": {
+            "type": "string"
+          },
+          "planetLocalized": {
+            "type": "string"
+          },
+          "sign": {
+            "type": "string"
+          },
+          "signLocalized": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "planet",
+          "sign",
+          "longitude"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "timezone": {
+      "type": "number"
+    },
+    "transitEvents": {
+      "items": {
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "datetime": {
+            "type": "string"
+          },
+          "fromSign": {
+            "type": "string"
+          },
+          "fromSignLocalized": {
+            "type": "string"
+          },
+          "isRetrograde": {
+            "type": "boolean"
+          },
+          "planet": {
+            "type": "string"
+          },
+          "planetLocalized": {
+            "type": "string"
+          },
+          "time": {
+            "type": "string"
+          },
+          "toSign": {
+            "type": "string"
+          },
+          "toSignLocalized": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "planet",
+          "fromSign",
+          "toSign",
+          "date",
+          "time",
+          "datetime",
+          "isRetrograde"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "year": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "year",
+    "month",
+    "timezone",
+    "startingPositions",
+    "transitEvents"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedAug 25, 2026

changedInput schema / properties / lang / description

Previous value: -"Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English."New value: +"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."

changedInput schema / properties / lang / enum

Previous value: -[
-  "en",
-  "tr",
-  "de",
-  "es",
-  "hi",
-  "pt",
-  "fr",
-  "ru"
-]New value: +[
+  "en",
+  "tr",
+  "de",
+  "es",
+  "hi",
+  "pt",
+  "fr",
+  "ru",
+  "zh-Hans",
+  "zh-Hant"
+]

AddedAug 17, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds substantial behavioral detail: it specifies the output (starting sign on first of month, each ingress with exact date/time in the user's timezone), the default window behavior when year/month are omitted, and verification against NASA JPL Horizons with cross-checks. This goes well beyond what annotations provide.

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 moderately long but well-structured: it front-loads the core purpose, then details the return format and default behavior, then use cases, and ends with verification. The only redundancy is the trailing keyword-like phrase ('Monthly transit API, planetary ingress calendar, sign change dates, tropical transit table.') which adds little value. Overall, it earns its length.

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?

The tool has 6 optional parameters and an output schema, so the description doesn't need to explain return values. It covers what the tool returns, defaults, timezone handling, and accuracy. It doesn't mention edge cases like DST or timezone resolution details, but those are covered in the schema. For a read-only data-retrieval tool, this is nearly complete.

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 each parameter already has a detailed description. The tool description adds marginal value by noting the 'omit year and month' behavior, but this is already implied by the schema defaults. It does not introduce syntax or formatting details beyond what the schema documents, so the baseline of 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?

The description states a specific verb ('Get') and a precise resource: every tropical sign change for a given month across all 14 Western bodies. It explicitly distinguishes itself from siblings like post_astrology_transits or post_astrology_planets_monthly by focusing on ingresses and naming the full body list, so an agent can select it unambiguously.

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?

The description provides clear use cases ('transit calendars, monthly forecast copy, retrograde and ingress tracking, newsletter automation') and explains the default month behavior when parameters are omitted. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5, but the context is sufficient for most selection decisions.

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

All Western Astrology MCP Server by RoxyAPI 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?