Western Astrology MCP Server by RoxyAPI

Monthly horoscope by zodiac sign - Editorial column with key dates

get_astrology_horoscope_sign_monthly

Read-only

A month-long column for any zodiac sign, plus a week-by-week breakdown and dated key dates a calendar page renders directly. The column names every aspect, ingress, lunation and station of the month and reads each into the whole-sign houses of that sign, and those events come back beside the prose with their exact instants, so a piece can be checked against NASA JPL Horizons or the US Naval Observatory before it runs. Key dates are the real New Moon, Full Moon and retrograde instants, never approximations. Alongside the column come overview, love, career, health, finance and advice. Pass any date inside a month to retrieve that month, or timezone to roll over on a local clock. Available in eight languages. Monthly horoscope API, zodiac monthly forecast, astrology monthly prediction.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Any date inside the target month, in YYYY-MM-DD format. The forecast covers the whole calendar month containing it. Defaults to the current period in the timezone parameter.
`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
`sign`	Yes	Zodiac sign, case-insensitive (e.g., aries, Aries, ARIES all work).
`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.
`timezone`	No	Selects which period counts as current when date is omitted. Defaults to UTC, so the forecast rolls over at 00:00 UTC on the 1st. Pass the timezone of the end user to roll over on their local clock instead. Ignored when date is set. Accepts an IANA name (e.g. "America/New_York"), decimal hours (e.g. 5.5 for IST), or a fixed UTC offset (e.g. "-05:00").

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so no contradiction exists. The description adds valuable behavioral guarantees beyond annotations: key dates are the exact New Moon, Full Moon, and retrograde instants ('never approximations'), and events can be verified against NASA JPL Horizons or USNO. It also discloses that the column includes all named aspects, ingresss, lunations, and stations read into whole-sign houses.

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 core paragraphs are dense and informative, front-loading the main purpose and key data guarantees. However, the final sentence 'Monthly horoscope API, zodiac monthly forecast, astrology monthly prediction.' is redundant SEO-style keyword-stuffing that provides no agent-usable guidance. The description could be tighten with out losing content.

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?

With no output schema, the description carries the burden of explaining return content: prose, week-by-week breakdown, dated key dates with exact instants, and companion overview/love/career/heath/finance/advice sections. It also covers month selection, timezone semantics, and language availability. A explicit note on the JSON response shape would make it fully complete, but it is already strong and actionable.

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 of 3 applies. The description adds a useful note that any date inside a month retrieves that month and that timezone affects the 'current' period, but the schema already fully documents all five parameters including formats, defaults, and examples. The description does not need to repeat parameter details.

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 states a specific service: a month-long horoscope column for any zodiac sign, including a week-by-week breakdown and dated key dates. The 'month-long' framing and final 'Monthly horoscope API' clearly distinguish it from the daily, weekly, and yearly sibling tools. The instruction 'Pass any date inside a month to retrieve that month' gives the agent a concrete retrieval pattern.

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?

Clear context is provided that this is the month-grade horoscope offering and how to select the target month with a date or timezone. It does not explicitly name the daily/weekly/yearly siblings or state when to prefer them, so it stops short of full alternative routing. The description still gives an agent enough context to pick this tool for monthly forecasts.

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?