Western Astrology MCP Server by RoxyAPI

Calculate house cusps - House system calculator with comparison

post_astrology_houses

Read-only

Calculate astrological house cusps using Placidus, Whole Sign, Equal, or Koch house systems. Returns all 12 house cusps with zodiac signs, degrees, Ascendant, and Midheaven. Use "all" parameter to compare all 4 house systems side-by-side. Perfect for astrology charts, house cusp tables, and educational tools showing house system differences. Includes accurate Ascendant and MC calculations.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes	Birth date in YYYY-MM-DD format. Date is critical for house cusp calculations as it determines planetary positions used in some house systems.
`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. Time is ESSENTIAL for accurate house cusps, and even minutes matter. The Ascendant (1st house cusp) changes roughly every 4 minutes. Without accurate time, house placements will be incorrect.
`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). Location determines the local horizon and meridian, which are fundamental to house division. Higher latitudes cause more distortion in time-based systems like Placidus.
`timezone`	Yes	Decimal hours from UTC (e.g. -5 for EST, 5.5 for IST, 9 for JST) OR IANA name (e.g. "America/New_York"). IANA resolved to the DST-correct offset for the chart date.
`longitude`	Yes	Birth location longitude in decimal degrees (-180 to 180). Affects local time and horizon calculations for house cusps.
`houseSystem`	No	House system for dividing ecliptic into 12 houses. Placidus (most popular) uses time, Whole Sign (ancient) uses signs, Equal divides from Ascendant. Use "all" to compare all 4 systems side-by-side for educational purposes.	placidus

Output Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes
`time`	Yes
`houses`	Yes
`latitude`	Yes
`timezone`	Yes
`ascendant`	Yes
`longitude`	Yes
`midheaven`	Yes
`comparison`	No
`houseSystem`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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"
+        }
+      },
+      "required": [
+        "sign",
+        "degree",
+        "longitude"
+      ],
+      "type": "object"
+    },
+    "comparison": {
+      "additionalProperties": {
+        "properties": {
+          "houses": {
+            "items": {
+              "properties": {
+                "degree": {
+                  "type": "number"
+                },
+                "longitude": {
+                  "type": "number"
+                },
+                "number": {
+                  "type": "number"
+                },
+                "sign": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "number",
+                "longitude",
+                "sign",
+                "degree"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "houses"
+        ],
+        "type": "object"
+      },
+      "type": "object"
+    },
+    "date": {
+      "type": "string"
+    },
+    "houseSystem": {
+      "type": "string"
+    },
+    "houses": {
+      "items": {
+        "properties": {
+          "degree": {
+            "type": "number"
+          },
+          "longitude": {
+            "type": "number"
+          },
+          "number": {
+            "type": "number"
+          },
+          "sign": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "number",
+          "longitude",
+          "sign",
+          "degree"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "latitude": {
+      "type": "number"
+    },
+    "longitude": {
+      "type": "number"
+    },
+    "midheaven": {
+      "properties": {
+        "degree": {
+          "type": "number"
+        },
+        "longitude": {
+          "type": "number"
+        },
+        "sign": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "sign",
+        "degree",
+        "longitude"
+      ],
+      "type": "object"
+    },
+    "time": {
+      "type": "string"
+    },
+    "timezone": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "date",
+    "time",
+    "latitude",
+    "longitude",
+    "timezone",
+    "houseSystem",
+    "ascendant",
+    "midheaven",
+    "houses"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 4, 2026

changedInput schema / properties / time / description

Previous value: -"Birth time in 24-hour HH:MM:SS format. Time is ESSENTIAL for accurate house cusps - even minutes matter. The Ascendant (1st house cusp) changes roughly every 4 minutes. Without accurate time, house placements will be incorrect."New value: +"Birth time in 24-hour HH:MM:SS format. Time is ESSENTIAL for accurate house cusps, and even minutes matter. The Ascendant (1st house cusp) changes roughly every 4 minutes. Without accurate time, house placements will be incorrect."

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

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.8/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 the capability to compare all four house systems and claims accurate Ascendant/MC calculations, but these are largely redundant with the output schema and parameter descriptions. No additional behavioral traits like rate limits or prerequisites are disclosed.

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 description is front-loaded with the core purpose, but it contains redundancy: 'Returns all 12 house cusps with zodiac signs, degrees, Ascendant, and Midheaven' is followed by 'Includes accurate Ascendant and MC calculations,' repeating the same information. The 'Perfect for' sentence is somewhat promotional and does not add technical value, so not every sentence earns its place.

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 read-only calculation tool with a rich output schema and fully described parameters, the description covers the essential context: what it computes, which systems are supported, and when comparison mode is useful. It does not address edge cases like high-latitude distortion or DST handling, but those are already documented in the schema descriptions, so the overall package is complete enough for an agent to call the tool correctly.

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 baseline is 3. The description mentions the 'all' parameter and house system options, but these are already described in the schema's houseSystem property. It does not add significant new meaning for individual parameters 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 opens with a specific verb and resource: 'Calculate astrological house cusps' and enumerates the supported systems (Placidus, Whole Sign, Equal, Koch). It clearly distinguishes this tool from siblings like post_astrology_aspects or post_astrology_natal_chart by focusing solely on house cusps and listing the specific output (cusps, Ascendant, Midheaven).

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 ('Perfect for astrology charts, house cusp tables, and educational tools showing house system differences') and highlights the 'all' parameter for side-by-side comparison. However, it does not explicitly state when not to use it or name alternative tools, stopping short of full usage 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 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?