Skip to main content
Glama

Western Astrology MCP Server by RoxyAPI

by com.roxyapi

Fixed stars and star conjunctions calculator - Regulus, Spica, Algol natal report

post_astrology_fixed_stars
Read-only

Calculate the tropical zodiac positions of the major named fixed stars for any birth moment, including the four Royal stars and the fifteen Behenian stars, then detect conjunctions to the natal planets, Ascendant, and Midheaven. Each star returns its precessed ecliptic longitude, zodiac sign, visual magnitude, and traditional planetary nature, with a plain language interpretation for every conjunction inside the chosen orb. A focused tool for natal reports that weigh Regulus, Spica, Aldebaran, Antares, and Algol against the chart.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orbNoConjunction orb in degrees, the maximum separation for a star to count as conjunct a chart point. Defaults to 1, maximum 3. Widen it to surface looser contacts or tighten it for only the closest hits.
dateYesBirth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.
langNoResponse 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
timeYesBirth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.
compactNoSet 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.
latitudeYesBirth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.
nodeTypeNoLunar 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
timezoneYesTimezone: 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.
longitudeYesBirth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already give exactly read/destructive hints, and the description goes well beyond them by disclosing each star's output and that each conjunction comes with a plain-language interpretation in the selected orb. This gives the agent a concrete model of the tool's behavior and return shape.

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?

Three sentences that front-load the main operational purpose, then list return details, and close with the use case. It is tidy, but there is slight redundancy between the groups of stars and the additional relisting of the five star names, so it isn't perfect.

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?

With a schema that already covers all parameters and a description that covers output details and orb sensitivity, an agent can select and invoke the tool confidently. No output schema is needed because the return semantics are fully described in prose.

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 offers 100% description coverage of all 9 parameters, so the baseline is 3. The description adds little to the parameter disambiguation; its only related note is 'chosen orb', which is indirectly redundant with the orb parameter's well-documented definition.

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 begins with a specific action and resource: 'Calculate the tropical zodiac positions of the major named fixed stars' and then states the exact use, detection of conjunctions to planets, Ascendant, and Midheaven. The list of star and the phrase 'focused tool for natal reports' distinguishes it from the many other astrological siblings without needing to open the schema.

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 makes the intended context clear: 'a focused tool for natal reports' that weighs Regulus, Spica, Aldebaran, Antares, and Algol against the chart. It does not explicitly name alternatives or when not to use it (e.g., not for planetary positions alone), so it stops short of a full usage guideline.

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