Western Astrology MCP Server by RoxyAPI

Transit Aspects - Detailed transit-to-natal aspect analysis with interpretations

post_astrology_transit_aspects

Read-only

Calculate all transit-to-natal aspects with detailed interpretations, strength ratings, and timing guidance. Compares current (or future) planetary positions against your natal chart to identify active transits. Returns aspect type, orb, applying/separating status, narrative interpretation, impact rating, and practical guidance for each transit. Like /astrology/transits with a natalChart, returns summary, timing, impact, guidance, and keywords for each aspect. Adds planet, aspect-type, and minStrength filtering plus summary.strongest and summary.byType rollups. Transit aspects API, transit-to-natal analysis, predictive astrology, personalized transit forecast.

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
`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	Filter to specific transiting planets. Omit to include all planets. Useful for focusing on slow-moving outer planet transits (Saturn, Jupiter, Pluto).
`natalChart`	Yes	Natal chart birth details (date, time, location, timezone). Used to calculate natal planetary positions that transits are compared against.
`aspectTypes`	No	Filter to specific aspect types (conjunction, opposition, trine, square, sextile, etc.). Omit to include all aspect types.
`houseSystem`	No	House system used to divide the natal chart into 12 houses. Every house number in the response is read against these natal cusps, for the natal bodies and the transiting bodies alike. Placidus (default) is time sensitive and the most widely used in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30 degree segments from the Ascendant. Koch emphasizes higher latitudes. Quadrant systems fall back to Whole Sign above the polar circle.	placidus
`minStrength`	No	Minimum aspect strength threshold (0-100). Higher values return only tighter, more potent aspects. Useful for filtering out wide-orb aspects.
`transitDate`	No	Transit date in YYYY-MM-DD format. Defaults to current date if omitted. Use future dates for predictive transit analysis.
`transitTime`	No	Transit time in HH:MM:SS format, read on the clock of the natal chart timezone at the transit date (an IANA zone takes the offset in force on that date, daylight saving included). Defaults to 12:00:00 (noon) if omitted.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`houses`	Yes
`aspects`	Yes
`summary`	Yes
`ascendant`	Yes
`houseSystem`	Yes
`transitDate`	Yes
`natalPlanets`	Yes
`transitPlanets`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 4, 2026

changedInput schema / examples

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

changedInput schema / properties / natalChart / properties / timezone / example
```
Previous value: --5New value: +"America/New_York"
```

Changed1 schema field changedOct 2, 2026

changedInput schema / properties / transitTime / description

Previous value: -"Transit time in HH:MM:SS format. Defaults to 12:00:00 (noon) if omitted."New value: +"Transit time in HH:MM:SS format, read on the clock of the natal chart timezone at the transit date (an IANA zone takes the offset in force on that date, daylight saving included). Defaults to 12:00:00 (noon) if omitted."

Changed1 schema field changedSep 23, 2026

changedInput schema / properties / natalChart / properties / timezone / description

Previous value: -"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly."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": {
+    "ascendant": {
+      "properties": {
+        "degree": {
+          "maximum": 30,
+          "minimum": 0,
+          "type": "number"
+        },
+        "longitude": {
+          "maximum": 360,
+          "minimum": 0,
+          "type": "number"
+        },
+        "sign": {
+          "type": "string"
+        },
+        "signLocalized": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "sign",
+        "degree",
+        "longitude"
+      ],
+      "type": "object"
+    },
+    "aspects": {
+      "items": {
+        "properties": {
+          "angle": {
+            "type": "number"
+          },
+          "interpretation": {
+            "enum": [
+              "harmonious",
+              "challenging",
+              "neutral"
+            ],
+            "type": "string"
+          },
+          "isApplying": {
+            "type": "boolean"
+          },
+          "orb": {
+            "type": "number"
+          },
+          "planet1": {
+            "enum": [
+              "Sun",
+              "Moon",
+              "Mercury",
+              "Venus",
+              "Mars",
+              "Jupiter",
+              "Saturn",
+              "Uranus",
+              "Neptune",
+              "Pluto",
+              "North Node",
+              "South Node",
+              "Chiron",
+              "Black Moon Lilith"
+            ],
+            "type": "string"
+          },
+          "planet1Localized": {
+            "type": "string"
+          },
+          "planet2": {
+            "enum": [
+              "Sun",
+              "Moon",
+              "Mercury",
+              "Venus",
+              "Mars",
+              "Jupiter",
+              "Saturn",
+              "Uranus",
+              "Neptune",
+              "Pluto",
+              "North Node",
+              "South Node",
+              "Chiron",
+              "Black Moon Lilith"
+            ],
+            "type": "string"
+          },
+          "planet2Localized": {
+            "type": "string"
+          },
+          "strength": {
+            "maximum": 100,
+            "minimum": 0,
+            "type": "number"
+          },
+          "transitInterpretation": {
+            "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"
+          },
+          "type": {
+            "enum": [
+              "CONJUNCTION",
+              "OPPOSITION",
+              "TRINE",
+              "SQUARE",
+              "SEXTILE",
+              "SEMI_SEXTILE",
+              "QUINCUNX",
+              "SEMI_SQUARE",
+              "SESQUIQUADRATE"
+            ],
+            "type": "string"
+          },
+          "typeLocalized": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "planet1",
+          "planet2",
+          "type",
+          "angle",
+          "orb",
+          "isApplying",
+          "strength",
+          "interpretation",
+          "transitInterpretation"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "houseSystem": {
+      "enum": [
+        "placidus",
+        "whole-sign",
+        "equal",
+        "koch"
+      ],
+      "type": "string"
+    },
+    "houses": {
+      "items": {
+        "properties": {
+          "degree": {
+            "maximum": 30,
+            "minimum": 0,
+            "type": "number"
+          },
+          "longitude": {
+            "maximum": 360,
+            "minimum": 0,
+            "type": "number"
+          },
+          "number": {
+            "maximum": 12,
+            "minimum": 1,
+            "type": "integer"
+          },
+          "sign": {
+            "type": "string"
+          },
+          "signLocalized": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "number",
+          "longitude",
+          "sign",
+          "degree"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "natalPlanets": {
+      "items": {
+        "properties": {
+          "degree": {
+            "maximum": 30,
+            "minimum": 0,
+            "type": "number"
+          },
+          "house": {
+            "maximum": 12,
+            "minimum": 1,
+            "type": "integer"
+          },
+          "isRetrograde": {
+            "type": "boolean"
+          },
+          "latitude": {
+            "type": "number"
+          },
+          "longitude": {
+            "maximum": 360,
+            "minimum": 0,
+            "type": "number"
+          },
+          "name": {
+            "enum": [
+              "Sun",
+              "Moon",
+              "Mercury",
+              "Venus",
+              "Mars",
+              "Jupiter",
+              "Saturn",
+              "Uranus",
+              "Neptune",
+              "Pluto",
+              "North Node",
+              "South Node",
+              "Chiron",
+              "Black Moon Lilith"
+            ],
+            "type": "string"
+          },
+          "nameLocalized": {
+            "type": "string"
+          },
+          "sign": {
+            "type": "string"
+          },
+          "signLocalized": {
+            "type": "string"
+          },
+          "speed": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "name",
+          "longitude",
+          "latitude",
+          "sign",
+          "degree",
+          "house",
+          "speed",
+          "isRetrograde"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "summary": {
+      "properties": {
+        "byType": {
+          "additionalProperties": {
+            "type": "number"
+          },
+          "type": "object"
+        },
+        "challenging": {
+          "type": "number"
+        },
+        "harmonious": {
+          "type": "number"
+        },
+        "neutral": {
+          "type": "number"
+        },
+        "strongest": {
+          "properties": {
+            "angle": {
+              "type": "number"
+            },
+            "interpretation": {
+              "enum": [
+                "harmonious",
+                "challenging",
+                "neutral"
+              ],
+              "type": "string"
+            },
+            "isApplying": {
+              "type": "boolean"
+            },
+            "orb": {
+              "type": "number"
+            },
+            "planet1": {
+              "enum": [
+                "Sun",
+                "Moon",
+                "Mercury",
+                "Venus",
+                "Mars",
+                "Jupiter",
+                "Saturn",
+                "Uranus",
+                "Neptune",
+                "Pluto",
+                "North Node",
+                "South Node",
+                "Chiron",
+                "Black Moon Lilith"
+              ],
+              "type": "string"
+            },
+            "planet1Localized": {
+              "type": "string"
+            },
+            "planet2": {
+              "enum": [
+                "Sun",
+                "Moon",
+                "Mercury",
+                "Venus",
+                "Mars",
+                "Jupiter",
+                "Saturn",
+                "Uranus",
+                "Neptune",
+                "Pluto",
+                "North Node",
+                "South Node",
+                "Chiron",
+                "Black Moon Lilith"
+              ],
+              "type": "string"
+            },
+            "planet2Localized": {
+              "type": "string"
+            },
+            "strength": {
+              "maximum": 100,
+              "minimum": 0,
+              "type": "number"
+            },
+            "transitInterpretation": {
+              "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"
+            },
+            "type": {
+              "enum": [
+                "CONJUNCTION",
+                "OPPOSITION",
+                "TRINE",
+                "SQUARE",
+                "SEXTILE",
+                "SEMI_SEXTILE",
+                "QUINCUNX",
+                "SEMI_SQUARE",
+                "SESQUIQUADRATE"
+              ],
+              "type": "string"
+            },
+            "typeLocalized": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "planet1",
+            "planet2",
+            "type",
+            "angle",
+            "orb",
+            "isApplying",
+            "strength",
+            "interpretation",
+            "transitInterpretation"
+          ],
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "total": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "total",
+        "harmonious",
+        "challenging",
+        "neutral",
+        "strongest",
+        "byType"
+      ],
+      "type": "object"
+    },
+    "transitDate": {
+      "type": "string"
+    },
+    "transitPlanets": {
+      "items": {
+        "properties": {
+          "degree": {
+            "maximum": 30,
+            "minimum": 0,
+            "type": "number"
+          },
+          "house": {
+            "maximum": 12,
+            "minimum": 1,
+            "type": "integer"
+          },
+          "isRetrograde": {
+            "type": "boolean"
+          },
+          "latitude": {
+            "type": "number"
+          },
+          "longitude": {
+            "maximum": 360,
+            "minimum": 0,
+            "type": "number"
+          },
+          "name": {
+            "enum": [
+              "Sun",
+              "Moon",
+              "Mercury",
+              "Venus",
+              "Mars",
+              "Jupiter",
+              "Saturn",
+              "Uranus",
+              "Neptune",
+              "Pluto",
+              "North Node",
+              "South Node",
+              "Chiron",
+              "Black Moon Lilith"
+            ],
+            "type": "string"
+          },
+          "nameLocalized": {
+            "type": "string"
+          },
+          "sign": {
+            "type": "string"
+          },
+          "signLocalized": {
+            "type": "string"
+          },
+          "speed": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "name",
+          "longitude",
+          "latitude",
+          "sign",
+          "degree",
+          "house",
+          "speed",
+          "isRetrograde"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "transitDate",
+    "houseSystem",
+    "houses",
+    "ascendant",
+    "transitPlanets",
+    "natalPlanets",
+    "aspects",
+    "summary"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 16, 2026

changedInput schema / properties / natalChart / properties / timezone / description

Previous value: -"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly."New value: +"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly."

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

Changed3 schema fields changedAug 17, 2026

addedInput schema / examples

Added value: +[
+  {
+    "natalChart": {
+      "date": "1990-07-15",
+      "latitude": 40.7128,
+      "longitude": -74.006,
+      "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."

changedInput schema / properties / natalChart / 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\"."

Changed1 schema field changedAug 10, 2026

addedInput schema / properties / natalChart / 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"
+}

Changed1 schema field changedAug 7, 2026

addedInput schema / properties / houseSystem

Added value: +{
+  "default": "placidus",
+  "description": "House system used to divide the natal chart into 12 houses. Every house number in the response is read against these natal cusps, for the natal bodies and the transiting bodies alike. Placidus (default) is time sensitive and the most widely used in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30 degree segments from the Ascendant. Koch emphasizes higher latitudes. Quadrant systems fall back to Whole Sign above the polar circle.",
+  "enum": [
+    "placidus",
+    "whole-sign",
+    "equal",
+    "koch"
+  ],
+  "example": "placidus",
+  "type": "string"
+}

Changed2 schema fields changedAug 2, 2026
- addedInput schema / properties / aspectTypes / example
```
Added value: +[
+  "CONJUNCTION",
+  "OPPOSITION",
+  "TRINE",
+  "SQUARE"
+]
```
- addedInput schema / properties / planets / example
```
Added value: +[
+  "Jupiter",
+  "Saturn",
+  "Pluto"
+]
```

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

Changed2 schema fields changedJul 12, 2026

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 / natalChart / properties / timezone / description

Previous value: -"Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. \"America/New_York\", \"Asia/Kolkata\"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly."New value: +"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly."

First observedJul 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish that this is a safe, read-only operation, so the bar is lower; the description still adds real context by enumerating the per-aspect outputs (aspect type, orb, applying/separating status, narrative interpretation, impact rating, practical guidance) and the summary rollups. It does not mention auth, rate limits, or cost despite being a POST compute-heavy endpoint, which keeps it short of a 5.

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 first three sentences are information-dense and front-loaded, but the closing string "Transit aspects API, transit-to-natal analysis, predictive astrology, personalized transit forecast" is keyword stuffing that adds no selection signal. The middle sentence partly duplicates the return-value sentence immediately before it (summary, timing, impact, guidance listed twice).

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 100% schema coverage, an output schema, and read-only annotations, the description needs only to establish purpose and the distinguishing feature set, which it does. The remaining gap is routing: nothing tells the agent why to choose this over post_astrology_transits or post_astrology_transits_monthly, which is a real risk given how many near-identical siblings exist.

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 documents all nine parameters in depth, establishing a baseline of 3. The description only restates that planet, aspect-type, and minStrength filtering exist; it adds no format or syntax detail beyond what the schema provides, so it neither compensates nor detracts.

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 and resource ("Calculate all transit-to-natal aspects") and then scopes it precisely: it explains that it compares current or future planetary positions against a natal chart, and that it adds planet/aspect-type/minStrength filtering plus summary.strongest and byType rollups on top of the base transits behavior. That contrast is enough to separate it from post_astrology_transits and post_astrology_aspects without opening a schema.

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?

Usage is only implied through the "Like /astrology/transits with a natalChart... Adds filtering" framing and the parenthetical "(or future)" positions. There is no explicit when-to-use or when-not-to-use statement picking between this tool, post_astrology_transits, and post_astrology_transits_monthly, so the agent must infer the choice from feature differences.

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?