Skip to main content
Glama

Western Astrology MCP Server by RoxyAPI

by com.roxyapi
OverviewDiscussionsAdmin

Calculate planetary transits - Current transits with natal chart comparison

post_astrology_transits
Read-only

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
NameRequiredDescriptionDefault
dateNoTransit date in YYYY-MM-DD format (defaults to current date)
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
timeNoTransit time in HH:MM:SS format (defaults to current time)
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.
nodeTypeNoLunar 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
timezoneNoTransit 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).
natalChartNoOptional natal chart data to compare transits against

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryNo
timezoneYes
transitDateYes
transitTimeYes
transitAspectsNo
transitPlanetsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "summary": {
+      "properties": {
+        "challenging": {
+          "type": "number"
+        },
+        "harmonious": {
+          "type": "number"
+        },
+        "neutral": {
+          "type": "number"
+        },
+        "totalAspects": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "totalAspects",
+        "harmonious",
+        "challenging",
+        "neutral"
+      ],
+      "type": "object"
+    },
+    "timezone": {
+      "type": "number"
+    },
+    "transitAspects": {
+      "items": {
+        "properties": {
+          "angle": {
+            "type": "number"
+          },
+          "interpretation": {
+            "properties": {
+              "guidance": {
+                "type": "string"
+              },
+              "impact": {
+                "type": "string"
+              },
+              "keywords": {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "summary": {
+                "type": "string"
+              },
+              "timing": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "summary",
+              "timing",
+              "impact",
+              "guidance",
+              "keywords"
+            ],
+            "type": "object"
+          },
+          "isApplying": {
+            "type": "boolean"
+          },
+          "natalPlanet": {
+            "type": "string"
+          },
+          "natalPlanetLocalized": {
+            "type": "string"
+          },
+          "nature": {
+            "type": "string"
+          },
+          "orb": {
+            "type": "number"
+          },
+          "strength": {
+            "type": "number"
+          },
+          "transitPlanet": {
+            "type": "string"
+          },
+          "transitPlanetLocalized": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          },
+          "typeLocalized": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "transitPlanet",
+          "natalPlanet",
+          "type",
+          "angle",
+          "orb",
+          "isApplying",
+          "strength",
+          "nature",
+          "interpretation"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "transitDate": {
+      "type": "string"
+    },
+    "transitPlanets": {
+      "items": {
+        "properties": {
+          "degree": {
+            "type": "number"
+          },
+          "isRetrograde": {
+            "type": "boolean"
+          },
+          "latitude": {
+            "type": "number"
+          },
+          "longitude": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "nameLocalized": {
+            "type": "string"
+          },
+          "sign": {
+            "type": "string"
+          },
+          "signLocalized": {
+            "type": "string"
+          },
+          "speed": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "name",
+          "longitude",
+          "latitude",
+          "sign",
+          "degree",
+          "speed",
+          "isRetrograde"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "transitTime": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "transitDate",
+    "transitTime",
+    "timezone",
+    "transitPlanets"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • 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"
+]
  3. Changed3 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
    • changedInput schema / properties / compact / description
      Previous value: -"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."New value: +"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."
    • changedInput schema / properties / nodeType / description
      Previous value: -"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 what most Western software reports (Astrolabe, Cafe Astrology, TimePassages), which is why it is the default here; astro-seek and the Steven Forrest evolutionary school use mean, so pass \"mean\" to match those. 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\"."New value: +"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\"."
  4. Changed1 schema field changed
    • addedInput schema / properties / nodeType
      Added value: +{
+  "default": "true",
+  "description": "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 what most Western software reports (Astrolabe, Cafe Astrology, TimePassages), which is why it is the default here; astro-seek and the Steven Forrest evolutionary school use mean, so pass \"mean\" to match those. 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\".",
+  "enum": [
+    "mean",
+    "true"
+  ],
+  "example": "true",
+  "type": "string"
+}
  5. Changed2 schema fields changed
    • addedInput schema / properties / natalChart / properties / latitude / description
      Added value: +"Natal birth latitude in decimal degrees, positive north. Sets the local sidereal time behind the natal Ascendant and house cusps that the transits are measured against."
    • addedInput schema / properties / natalChart / properties / longitude / description
      Added value: +"Natal birth longitude in decimal degrees, positive east and negative west. Example: New York -74.0060, London -0.1276, Sydney 151.2093."
  6. Changed1 schema field changed
    • changedInput schema / properties / compact / description
      Previous value: -"Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false."New value: +"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."
  7. Changed1 schema field changed
    • addedInput schema / properties / compact
      Added value: +{
+  "default": false,
+  "description": "Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false.",
+  "type": "boolean"
+}
  8. Changed2 schema fields changed
    • changedInput schema / properties / natalChart / properties / timezone / anyOf
      Previous value: -[
-  {
-    "maximum": 14,
-    "minimum": -14,
-    "type": "number"
-  },
-  {
-    "pattern": "^[A-Za-z_]+(?:\\/[A-Za-z0-9_+-]+){0,2}$",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 14,
+    "minimum": -14,
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]
    • changedInput schema / properties / timezone / anyOf
      Previous value: -[
-  {
-    "maximum": 14,
-    "minimum": -14,
-    "type": "number"
-  },
-  {
-    "pattern": "^[A-Za-z_]+(?:\\/[A-Za-z0-9_+-]+){0,2}$",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 14,
+    "minimum": -14,
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]
  9. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context: it returns all 14 celestial bodies with signs, degrees, and speeds, and when a natal chart is supplied it includes aspect orbs and applying/separating status. This goes beyond the annotations without contradicting them.

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

Conciseness5/5

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

Four sentences front-load the verb and scope, then move from output details to the optional mode to use cases. There is no filler, no repetition of schema content, and every sentence earns its place.

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

Completeness5/5

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

The tool has a rich output schema and a fully documented parameter schema, and the description adds the missing high-level output summary and use-case context. All 7 parameters and both enum options are documented in the schema, so the only minor gap is explicit sibling 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?

The input schema covers 100% of parameters with detailed descriptions, so the baseline is 3. The description reinforces the optional natalChart use case and 'future transits' semantics but does not add syntax-level detail beyond what the schema already provides.

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 uses a specific verb ('Calculate'), names the resource ('current or future planetary transits'), and clarifies the optional natal-chart comparison. This distinguishes it from transit-related sibling tools like post_astrology_transits_monthly and post_astrology_transit_aspects.

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?

It clearly states the intended use cases ('daily transit forecasts, aspect alerts, and personalized transit reports') and when natal data should be provided. It does not explicitly name sibling alternatives or exclusion conditions, so it falls just short of full routing guidance.

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 toolsInspect
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