Western Astrology MCP Server by RoxyAPI

Generate natal chart - Birth chart calculator API with houses and aspects

post_astrology_natal_chart

Read-only

Calculate complete Western astrology natal chart (birth chart) with tropical zodiac. Returns all 14 celestial bodies (the 10 classical planets Sun through Pluto, the lunar nodes, Chiron, and Black Moon Lilith), 12 house cusps with customizable house systems (Placidus, Whole Sign, Equal, Koch), major and minor aspects, Ascendant, Midheaven, dominant elements and modalities. Perfect for astrology apps, birth chart generators, horoscope websites, and astrological consultation tools. Verified against NASA JPL Horizons.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes	Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.
`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	Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.
`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.
`latitude`	Yes	Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.
`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`	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.
`longitude`	Yes	Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.
`houseSystem`	No	House system for dividing the chart into 12 houses. Placidus (default) is most popular in Western astrology and time-sensitive. Whole Sign assigns one sign per house (simpler, ancient). Equal houses divide chart into 30° segments from Ascendant. Koch emphasizes houses in high latitudes.	placidus

Output Schema

TableJSON Schema

Name	Required	Description	Default
`houses`	Yes
`vertex`	Yes
`aspects`	Yes
`planets`	Yes
`summary`	Yes
`patterns`	No
`ascendant`	Yes
`midheaven`	Yes
`houseSystem`	Yes
`birthDetails`	Yes
`partOfFortune`	Yes
`aspectsInterpretation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 4, 2026

changedInput schema / examples

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

changedInput schema / properties / timezone / example

Previous value: --5New value: +"America/New_York"

Changed1 schema field changedSep 23, 2026

changedInput schema / 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": {
+          "type": "number"
+        },
+        "longitude": {
+          "type": "number"
+        },
+        "sign": {
+          "type": "string"
+        },
+        "signLocalized": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "sign",
+        "degree",
+        "longitude"
+      ],
+      "type": "object"
+    },
+    "aspects": {
+      "items": {
+        "properties": {
+          "angle": {
+            "type": "number"
+          },
+          "aspectInterpretation": {
+            "properties": {
+              "keywords": {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "summary": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "summary",
+              "keywords"
+            ],
+            "type": "object"
+          },
+          "interpretation": {
+            "type": "string"
+          },
+          "isApplying": {
+            "type": "boolean"
+          },
+          "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",
+          "aspectInterpretation"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "aspectsInterpretation": {
+      "properties": {
+        "challenging": {
+          "type": "number"
+        },
+        "dominant": {
+          "type": "string"
+        },
+        "harmonious": {
+          "type": "number"
+        },
+        "neutral": {
+          "type": "number"
+        },
+        "summary": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "summary",
+        "dominant",
+        "harmonious",
+        "challenging",
+        "neutral"
+      ],
+      "type": "object"
+    },
+    "birthDetails": {
+      "properties": {
+        "date": {
+          "type": "string"
+        },
+        "latitude": {
+          "type": "number"
+        },
+        "longitude": {
+          "type": "number"
+        },
+        "time": {
+          "type": "string"
+        },
+        "timezone": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "date",
+        "time",
+        "latitude",
+        "longitude",
+        "timezone"
+      ],
+      "type": "object"
+    },
+    "houseSystem": {
+      "type": "string"
+    },
+    "houses": {
+      "items": {
+        "properties": {
+          "degree": {
+            "type": "number"
+          },
+          "longitude": {
+            "type": "number"
+          },
+          "number": {
+            "type": "number"
+          },
+          "sign": {
+            "type": "string"
+          },
+          "signLocalized": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "number",
+          "longitude",
+          "sign",
+          "degree"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "midheaven": {
+      "properties": {
+        "degree": {
+          "type": "number"
+        },
+        "longitude": {
+          "type": "number"
+        },
+        "sign": {
+          "type": "string"
+        },
+        "signLocalized": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "sign",
+        "degree",
+        "longitude"
+      ],
+      "type": "object"
+    },
+    "partOfFortune": {
+      "properties": {
+        "degree": {
+          "maximum": 30,
+          "minimum": 0,
+          "type": "number"
+        },
+        "house": {
+          "maximum": 12,
+          "minimum": 1,
+          "type": "integer"
+        },
+        "longitude": {
+          "maximum": 360,
+          "minimum": 0,
+          "type": "number"
+        },
+        "sect": {
+          "enum": [
+            "day",
+            "night"
+          ],
+          "type": "string"
+        },
+        "sign": {
+          "type": "string"
+        },
+        "signLocalized": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "sign",
+        "degree",
+        "longitude",
+        "house",
+        "sect"
+      ],
+      "type": "object"
+    },
+    "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"
+    },
+    "planets": {
+      "items": {
+        "properties": {
+          "degree": {
+            "type": "number"
+          },
+          "dignity": {
+            "enum": [
+              "domicile",
+              "exaltation",
+              "detriment",
+              "fall",
+              "peregrine"
+            ],
+            "type": "string"
+          },
+          "house": {
+            "type": "number"
+          },
+          "interpretation": {
+            "properties": {
+              "detailed": {
+                "type": "string"
+              },
+              "keywords": {
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "summary": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "summary",
+              "detailed",
+              "keywords"
+            ],
+            "type": "object"
+          },
+          "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",
+          "house",
+          "speed",
+          "isRetrograde"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "summary": {
+      "properties": {
+        "dominantElement": {
+          "type": "string"
+        },
+        "dominantElementLocalized": {
+          "type": "string"
+        },
+        "dominantModality": {
+          "type": "string"
+        },
+        "dominantModalityLocalized": {
+          "type": "string"
+        },
+        "elementDistribution": {
+          "additionalProperties": {
+            "type": "number"
+          },
+          "type": "object"
+        },
+        "modalityDistribution": {
+          "additionalProperties": {
+            "type": "number"
+          },
+          "type": "object"
+        },
+        "retrogradePlanets": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "retrogradePlanetsLocalized": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "dominantElement",
+        "dominantModality",
+        "retrogradePlanets",
+        "elementDistribution",
+        "modalityDistribution"
+      ],
+      "type": "object"
+    },
+    "vertex": {
+      "properties": {
+        "degree": {
+          "maximum": 30,
+          "minimum": 0,
+          "type": "number"
+        },
+        "house": {
+          "maximum": 12,
+          "minimum": 1,
+          "type": "integer"
+        },
+        "longitude": {
+          "maximum": 360,
+          "minimum": 0,
+          "type": "number"
+        },
+        "sign": {
+          "type": "string"
+        },
+        "signLocalized": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "sign",
+        "degree",
+        "longitude",
+        "house"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "birthDetails",
+    "planets",
+    "houses",
+    "houseSystem",
+    "aspects",
+    "aspectsInterpretation",
+    "ascendant",
+    "midheaven",
+    "partOfFortune",
+    "vertex",
+    "summary"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 16, 2026

changedInput schema / 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: +[
+  {
+    "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 / 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 / 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 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 / 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 / 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.7/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 the safety profile is covered. The description adds that the calculation uses the tropical zodiac and is 'Verified against NASA JPL Horizons,' which is a useful accuracy signal, but it does not disclose rate limits, authentication needs, or other operational behavior; much of the remaining text restates return contents that the output schema covers.

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 first sentence is front-loaded with the core purpose and return contents, and the final accuracy claim is useful. The middle marketing sentence ('Perfect for...') does not help an agent invoke the tool and could be removed, but overall the description is appropriately sized.

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?

For a 9-parameter, read-only calculation tool with full schema coverage, an output schema, and safety annotations, the description provides enough context about scope and outputs. It does not need to explain return values because an output schema exists, though it could better route agents among the many sibling chart tools.

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 all nine parameters—including the house system enum and node type—are already fully documented in the input schema. The description mentions customizable house systems but adds no syntax, defaults, or constraints beyond what the schema 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?

States a specific verb ('Calculate') and resource ('Western astrology natal chart'), and enumerates the returned bodies, houses, aspects, Ascendant, Midheaven, and dominants. This distinguishes it from narrower sibling tools like post_astrology_planets or post_astrology_houses, which each return a subset.

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 astrology apps, birth chart generators, horoscope websites, and astrological consultation tools,' which implies usage context but never states when to choose this complete-chart tool over siblings like post_astrology_planets or post_astrology_aspects. No exclusions or prerequisites are given.

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?