RoxyAPI Astrology MCP server

Official

by RoxyAPI

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

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

post_astrology_fixed_stars

Read-only

Compute fixed star positions and conjunctions to natal planets, Ascendant, and Midheaven for any birth moment, returning zodiac signs, magnitudes, and interpretations.

Instructions

Calculate the tropical zodiac positions of the major named fixed stars for any birth moment. Covers the four Royal stars and the fifteen Behenian stars, then detects 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

Name	Required	Description	Default
`orb`	No	Conjunction 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.
`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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`orb`	Yes
`stars`	Yes
`summary`	Yes
`birthDetails`	Yes
`conjunctions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

A4/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 read-only safety profile is covered. The description adds context about what the tool computes (precessed longitudes, conjunctions, plain language interpretations) but does not go into side effects, rate limits, or auth requirements. This is acceptable given the annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, each with a distinct purpose: action, scope, output details, and use case. No fluff or redundancy. The core purpose is front-loaded, and the description earns its length.

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?

Given the output schema exists and the annotations cover safety, the description is complete for a well-scoped tool: it explains the star coverage, the conjunction detection, and the use case. It could explicitly name sibling tools for other calculations, but the title and sibling list make the boundary clear enough.

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% (all 9 parameters are documented), so the baseline is 3. The tool description mentions the 'chosen orb' but does not add meaningful parameter semantics beyond what the schema already explains, such as orb's min/max/default or timezone resolution rules. 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 names a specific verb and resource ('Calculate the tropical zodiac positions of the major named fixed stars') and delineates scope ('four Royal stars and the fifteen Behenian stars', conjunctions to planets, Ascendant, Midheaven). It clearly distinguishes itself from siblings like post_astrology_planets or post_astrology_asteroids by focusing on fixed stars and their conjunctions.

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 context: 'A focused tool for natal reports that weigh Regulus, Spica, Aldebaran, Antares, and Algol against the chart.' This implies when to use it (natal star analysis) but does not explicitly mention alternative tools or state when not to use it. Still, the use case is concrete and distinguishes it from other chart tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server