Western Astrology MCP Server by RoxyAPI

Weekly horoscope by zodiac sign - Seven-day editorial column

get_astrology_horoscope_sign_weekly

Read-only

A Monday to Sunday column for any zodiac sign, naming the transits that perfect during the week and the days they fall on. Each event is read into the whole-sign houses of that sign, so content is unique per sign, and the dated events come back beside the prose so an editor can check a piece before it runs. Alongside the column come overview, love, career, health, finance and advice, plus lucky days, lucky numbers and compatible signs. No language model is involved, so the same sign and week always returns the same text. Pass any date inside a week to retrieve that week, or timezone to roll over on a local clock. Composed in 8 languages (en, de, es, fr, hi, pt, ru, tr); any other lang code returns English. Weekly horoscope API, zodiac weekly forecast, astrology weekly prediction.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Any date inside the target week, in YYYY-MM-DD format. The forecast covers the Monday to Sunday week 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 each Monday. 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").

Output Schema

TableJSON Schema

Name	Required	Description	Default
`love`	Yes
`sign`	Yes
`week`	Yes
`advice`	Yes
`career`	Yes
`column`	Yes
`events`	Yes
`health`	Yes
`finance`	Yes
`overview`	Yes
`luckyDays`	Yes
`luckyNumbers`	Yes
`compatibleSigns`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "advice": {
+      "type": "string"
+    },
+    "career": {
+      "type": "string"
+    },
+    "column": {
+      "type": "string"
+    },
+    "compatibleSigns": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "events": {
+      "items": {
+        "properties": {
+          "aspect": {
+            "type": "string"
+          },
+          "at": {
+            "type": "string"
+          },
+          "bodies": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "house": {
+            "maximum": 12,
+            "minimum": 1,
+            "type": "integer"
+          },
+          "sign": {
+            "type": "string"
+          },
+          "through": {
+            "type": "string"
+          },
+          "type": {
+            "enum": [
+              "aspect",
+              "sign-ingress",
+              "retrograde-station",
+              "lunar-phase",
+              "eclipse",
+              "solar-season"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "type",
+          "at",
+          "bodies",
+          "house"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "finance": {
+      "type": "string"
+    },
+    "health": {
+      "type": "string"
+    },
+    "love": {
+      "type": "string"
+    },
+    "luckyDays": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "luckyNumbers": {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "overview": {
+      "type": "string"
+    },
+    "sign": {
+      "type": "string"
+    },
+    "week": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "sign",
+    "week",
+    "overview",
+    "love",
+    "career",
+    "health",
+    "finance",
+    "advice",
+    "column",
+    "events",
+    "luckyDays",
+    "luckyNumbers",
+    "compatibleSigns"
+  ],
+  "type": "object"
+}

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: +[
+  {
+    "sign": "aries"
+  }
+]

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

Changed2 schema fields changedJul 31, 2026

addedInput schema / properties / date

Added value: +{
+  "description": "Any date inside the target week, in YYYY-MM-DD format. The forecast covers the Monday to Sunday week containing it. Defaults to the current period in the timezone parameter.",
+  "example": "2026-04-03",
+  "format": "date",
+  "type": "string"
+}

addedInput schema / properties / timezone

Added value: +{
+  "description": "Selects which period counts as current when date is omitted. Defaults to UTC, so the forecast rolls over at 00:00 UTC on each Monday. 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\").",
+  "example": "America/New_York",
+  "type": "string"
+}

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"
+}

First observedJul 8, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The description discloses behaviors not available in the annotations: deterministic output ('No language model is involved, so the same sign and week always returns the same text'), language fallback ('any other lang code returns English'), timezone-sensitive week rollover, and uniqueness of content per sign. This adds substantial context beyond the readOnlyHint/destructiveHint annotations. No contradiction exists.

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 organized and front-loads the core purpose, but it is longer than necessary and ends with a keyword-stuffed sentence ('Weekly horoscope API, zodiac weekly forecast, astrology weekly prediction') that adds no agent value. Several behavioral details are repeated in the schema, 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?

Given that an output schema exists, the description correctly avoids restating return formats. It covers what the column contains (overview, love, career, health, finance, advice, lucky days, numbers, compatible signs), determinism, date/timezone behavior, and language fallback. The only minor gap is not explicitly distinguishing when to prefer this over the daily/monthly siblings, though the Monday-to-Sunday framing makes it inferable.

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 reinforces parameter semantics (e.g., 'Pass any date inside a week to retrieve that week' for date, 'timezone to roll over on a local clock' for timezone, and language fallback), but it doesn't introduce meaning beyond what the schema already documents. This is adequate but not additive.

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 clearly states the resource: a Monday-to-Sunday horoscope column for any zodiac sign, naming transits and the days they fall on. The 'Monday to Sunday' framing sharply distinguishes it from daily and monthly sibling tools. The verb 'retrieve' appears in the date-handling sentence, making the action explicit.

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 gives clear operational context: pass any date inside a week to select that week, omit date to use the current period, and pass a timezone to control the local rollover. It doesn't explicitly say 'use this instead of the daily/monthly tools,' but the weekly scope and content list make the intended use obvious. No exclusions or alternative routing are stated.

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?