Western Astrology MCP Server by RoxyAPI

Calculate planetary aspects - Aspect finder for any date and time

post_astrology_aspects

Read-only

Calculate all major and minor aspects between planets for any date and time. Finds conjunctions (0°), oppositions (180°), trines (120°), squares (90°), sextiles (60°), and minor aspects. Returns aspect type, exact angle, orb, applying/separating status, and strength (0-100). Filter by specific planets or aspect types. Perfect for aspect tables, transit analysis, and aspect pattern detection. Uses standard Western astrology orbs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes	Date in YYYY-MM-DD format
`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	Time in HH:MM:SS format (24-hour)
`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.
`planets`	No	Optional: specific bodies to calculate aspects for (defaults to all 14: the 10 classical planets, the lunar nodes, Chiron, and Black Moon Lilith)
`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.
`aspectTypes`	No	Optional: specific aspect types to find (defaults to all 9)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes
`time`	Yes
`aspects`	Yes
`summary`	Yes
`patterns`	No
`timezone`	Yes
`aspectsFound`	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 decimal hours (NOT minutes format). Examples: New York EST = -5, India IST = 5.5 (NOT 5:30), Tokyo JST = 9. IMPORTANT: Use decimal format (5.5, not 5:30)."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 to the offset in force at the given date and time."

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "aspects": {
+      "items": {
+        "properties": {
+          "angle": {
+            "type": "number"
+          },
+          "interpretation": {
+            "type": "string"
+          },
+          "isApplying": {
+            "type": "boolean"
+          },
+          "meaning": {
+            "properties": {
+              "description": {
+                "properties": {
+                  "long": {
+                    "type": "string"
+                  },
+                  "short": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "short",
+                  "long"
+                ],
+                "type": "object"
+              },
+              "keywords": {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "name": {
+                "type": "string"
+              },
+              "nature": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "name",
+              "description",
+              "keywords",
+              "nature"
+            ],
+            "type": "object"
+          },
+          "orb": {
+            "type": "number"
+          },
+          "planet1": {
+            "type": "string"
+          },
+          "planet1Localized": {
+            "type": "string"
+          },
+          "planet2": {
+            "type": "string"
+          },
+          "planet2Localized": {
+            "type": "string"
+          },
+          "strength": {
+            "type": "number"
+          },
+          "type": {
+            "type": "string"
+          },
+          "typeLocalized": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "planet1",
+          "planet2",
+          "type",
+          "angle",
+          "orb",
+          "isApplying",
+          "strength",
+          "interpretation"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "aspectsFound": {
+      "type": "number"
+    },
+    "date": {
+      "type": "string"
+    },
+    "patterns": {
+      "items": {
+        "properties": {
+          "apex": {
+            "type": "string"
+          },
+          "dissociate": {
+            "type": "boolean"
+          },
+          "element": {
+            "enum": [
+              "fire",
+              "earth",
+              "air",
+              "water"
+            ],
+            "type": "string"
+          },
+          "interpretation": {
+            "type": "string"
+          },
+          "interpretationKey": {
+            "type": "string"
+          },
+          "interpretationVars": {
+            "additionalProperties": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "kind": {
+            "enum": [
+              "GRAND_TRINE",
+              "KITE",
+              "T_SQUARE",
+              "GRAND_CROSS",
+              "YOD",
+              "MYSTIC_RECTANGLE",
+              "STELLIUM"
+            ],
+            "type": "string"
+          },
+          "modality": {
+            "enum": [
+              "cardinal",
+              "fixed",
+              "mutable"
+            ],
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "planets": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "tightness": {
+            "maximum": 100,
+            "minimum": 0,
+            "type": "number"
+          }
+        },
+        "required": [
+          "kind",
+          "name",
+          "planets",
+          "tightness",
+          "interpretation",
+          "interpretationKey",
+          "interpretationVars"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "summary": {
+      "properties": {
+        "byType": {
+          "additionalProperties": {
+            "type": "number"
+          },
+          "type": "object"
+        },
+        "challenging": {
+          "type": "number"
+        },
+        "harmonious": {
+          "type": "number"
+        },
+        "neutral": {
+          "type": "number"
+        },
+        "totalAspects": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "totalAspects",
+        "harmonious",
+        "challenging",
+        "neutral",
+        "byType"
+      ],
+      "type": "object"
+    },
+    "time": {
+      "type": "string"
+    },
+    "timezone": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "date",
+    "time",
+    "timezone",
+    "aspectsFound",
+    "aspects",
+    "summary"
+  ],
+  "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"
+]

Changed2 schema fields changedAug 17, 2026

addedInput schema / examples

Added value: +[
+  {
+    "date": "1990-07-15",
+    "time": "14:30:00",
+    "timezone": -5
+  }
+]

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."

Changed1 schema field changedJul 22, 2026

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."

Changed1 schema field changedJul 22, 2026

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"
+}

Changed1 schema field changedJul 12, 2026

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"
+  }
+]

First observedJul 8, 2026

TDQS

A3.7/5.0

Behavior4/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 covered. The description adds useful behavioral context beyond annotations: it states that the tool returns applying/separating status and a 0-100 strength, supports filtering, and uses 'standard Western astrology orbs.' This helps set expectations about output richness and orb conventions without contradicting the annotations.

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 compact and front-loaded: it opens with the core action, then defines aspect types, output fields, filtering, use cases, and orb conventions. Every sentence contributes information, and there is no filler or tautological restatement of the tool name. The use-case list is brief but adds useful context.

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 a detailed input schema (100% coverage), an output schema, and read-only annotations, the description is largely sufficient for an agent to select and invoke the tool. It covers the single date/time scope, output highlights, filtering, and orb conventions. The main missing piece is explicit sibling differentiation, but that is already accounted for in usage guidelines.

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 fully documents date, time, timezone, lang, compact, planets, and aspectTypes. The description only reinforces that planets and aspectTypes can filter results and that minor aspects are included by default, adding little beyond the schema. This matches the baseline of 3 for high schema coverage.

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?

The description uses a specific verb and resource: 'Calculate all major and minor aspects between planets for any date and time,' and it enumerates the output fields (aspect type, angle, orb, applying/separating status, strength). This clearly states what the tool does. It does not explicitly contrast the tool with nearby siblings like post_astrology_aspects_monthly or post_astrology_transit_aspects, so sibling differentiation is only implicit.

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?

The description says it is 'Perfect for aspect tables, transit analysis, and aspect pattern detection,' which gives use cases but no decision rule for choosing this tool over alternatives. With sibling tools such as post_astrology_aspects_monthly, post_astrology_transit_aspects, and post_astrology_aspect_patterns present, explicit guidance about when to use this tool versus those would help. No exclusions or alternative routing are provided.

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?