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

TDQS

A4.2/5.0

Behavior4/5

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

With readOnlyHint=true and destructiveHint=false already present, the description adds useful behavioral context by detailing the return values and mentioning Ascendant and Midheaven correctness. There is no contradiction, and no side-effect concerns beyond what annotations cover.

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, with the core verb and scope in the first sentence. The final 'Includes accurate Ascendant and MC calculations' is slightly redundant with the return-values sentence, but the overall structure is informative and free of fluff.

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?

Even though there is no output schema, the description explicitly covers what the agent can expect in return, which is the main missing contextual piece. The schema covers all inputs, and the annotations cover the safety profile, so nothing needed to invoke the tool confidently is missing.

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 already documents every parameter with 100% coverage, including defaults, formats, enums, and examples, so the baseline applies. The description adds only the meaning of the 'all' parameter, which the schema also already explains; it does not need to re-explain the other parameters.

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 object ('Calculate astrological house cusps') and names the four supported house systems, immediately distinguishing this tool from the many sibling astrology tools. It also specifies outputs: all 12 cusps, signs, degrees, Ascendant, and 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?

It provides clear usage context by suggesting it for astrology charts, house cusp tables, and education, and explicitly instructs to pass 'all' for side-by-side comparison of house systems. It doesn't name when-not-to-use alternatives, but the specific subject matter makes the intended scope clear.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation3/5

Most tools are scoped to a clearly distinct domain—moon phases, houses, returns, fixed stars, astrocartography—but several pairs overlap, notably synastry vs. compatibility_score and transits vs. transit_aspects. The descriptions are long and do help an agent choose, but the boundaries are not always obvious at the name level.

Naming Consistency4/5

Every tool follows the same snake_case get_astrology_/post_astrology_ prefix pattern, making the group predictable and readable. However, collection endpoints like get_astrology_planet_meanings_id and get_astrology_signs_id awkwardly combine plural collection and singular id naming, and names like calendar_year_month depart from the cleaner resource+suffix pattern.

Tool Count2/5

With 38 tools, this is well over the 25+ threshold and feels heavy for an agent to traverse. While Western astrology is a broad domain, several near-duplicate endpoints, especially synastry/compatibility and transits/transit_aspects, could be consolidated into fewer, more scoped tools.

Completeness5/5

The toolset is comprehensive, covering natal charts, relationships, transits, returns, progressions, aspects, houses, relocation, and reference data. It includes enough specialized endpoints for both casual horoscope use and in-depth astrological analysis, with no obvious dead ends for the stated domain.

Resources

Need Help?