Western Astrology MCP Server by RoxyAPI

Get zodiac sign details - Complete astrology sign profile with personality traits

get_astrology_signs_id

Read-only

Retrieve comprehensive zodiac sign information for any astrological sign using lowercase ID (e.g., "aries") or case-insensitive name (e.g., "Aries", "ARIES"). Returns complete astrology profile including: element (fire, earth, air, water), modality (cardinal, fixed, mutable), ruling planet, birth date ranges, personality traits (positive, negative, keywords), zodiac sign descriptions, famous people with this sign, key strengths and qualities, sign motto, greatest gifts, challenges, and secret weapon. Perfect for horoscope readings, zodiac compatibility checks, birth chart interpretations, astrology blogs, star sign personality analysis, and zodiac meaning databases.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Sign ID (lowercase, e.g., aries, taurus) or display name (case-insensitive, e.g., Aries, TAURUS).
`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
`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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`dates`	Yes
`gifts`	No
`motto`	No
`famous`	No
`symbol`	No
`weapon`	No
`element`	Yes
`keywords`	Yes
`modality`	Yes
`strengths`	No
`challenges`	No
`symbolName`	Yes
`description`	Yes
`rulingPlanet`	Yes
`compatibleSigns`	Yes
`elementLocalized`	No
`modalityLocalized`	No
`rulingPlanetLocalized`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "challenges": {
+      "type": "string"
+    },
+    "compatibleSigns": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "dates": {
+      "properties": {
+        "end": {
+          "type": "string"
+        },
+        "start": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "start",
+        "end"
+      ],
+      "type": "object"
+    },
+    "description": {
+      "properties": {
+        "long": {
+          "type": "string"
+        },
+        "short": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "short",
+        "long"
+      ],
+      "type": "object"
+    },
+    "element": {
+      "enum": [
+        "fire",
+        "earth",
+        "air",
+        "water"
+      ],
+      "type": "string"
+    },
+    "elementLocalized": {
+      "type": "string"
+    },
+    "famous": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "gifts": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "keywords": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "modality": {
+      "enum": [
+        "cardinal",
+        "fixed",
+        "mutable"
+      ],
+      "type": "string"
+    },
+    "modalityLocalized": {
+      "type": "string"
+    },
+    "motto": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "rulingPlanet": {
+      "type": "string"
+    },
+    "rulingPlanetLocalized": {
+      "type": "string"
+    },
+    "strengths": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "symbol": {
+      "type": "string"
+    },
+    "symbolName": {
+      "type": "string"
+    },
+    "weapon": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "symbolName",
+    "element",
+    "modality",
+    "rulingPlanet",
+    "dates",
+    "keywords",
+    "description",
+    "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: +[
+  {
+    "id": "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."

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

A3.5/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, covering the safety profile. The description adds meaningful behavioral context: input flexibility (lowercase ID or case-insensitive name) and the comprehensive nature of the response. It does not contradict annotations and provides extra detail about what the call returns without relying solely on the schema.

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

Conciseness2/5

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

The description is a single, long, run-on sentence that packs a massive enumeration of returned fields ('...personality traits (positive, negative, keywords), zodiac sign descriptions, famous people with this sign, key strengths and qualities, sign motto, greatest gifts, challenges, and secret weapon.'). It is not front-loaded with the most critical differentiators and would be easier to scan if split into short sentences or bullets. This length reduces usability.

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?

The tool has an output schema, so return-value explanation is unnecessary. The description covers input formats, language options via schema, and the breadth of returned data. It does not mention error handling or edge cases (e.g., unknown sign IDs), but for a simple read-by-ID tool with read-only annotations, the description is sufficiently complete for an agent to call it correctly.

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 coverage is 100% — every parameter (id, lang, compact) has a description in the input schema. The tool description essentially repeats the id input behavior (lowercase or case-insensitive) that the schema already documents, adding no new semantic value. It does not elaborate on lang or compact beyond what the schema states. Since schema carries the full burden, a baseline 3 is appropriate.

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 ('Retrieve') and a clear resource ('comprehensive zodiac sign information'), then enumerates the exact fields returned (element, modality, ruling planet, personality traits, etc.). It is unambiguous about what the tool does and is not a tautology. However, it does not explicitly contrast with the sibling get_astrology_signs (likely a list-all tool), so it slightly misses sibling differentiation, but the purpose itself is crystal clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description lists broad use cases ('Perfect for horoscope readings, zodiac compatibility checks...') but gives no guidance on when to choose this tool over alternatives. It does not mention get_astrology_signs (which likely returns all signs) or any condition that would make this tool inappropriate. The implication that it handles a single sign is present but not explicit, and there is no when-not-to-use guidance.

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?