Chinese Astrology MCP Server by RoxyAPI

Daily Chinese zodiac reading - Day pillar forecast by animal sign

get_chinese_astrology_zodiac_id_daily

Read-only

Get the daily reading for one Chinese zodiac animal, built from the sexagenary day pillar rather than from a rotation of stock text. The day carries its own Earthly Branch, that branch stands in exactly one of six classical relations to the requested sign, and the reading is that relation applied to the sign temperament. Returns the day pillar, the relation, an energy rating, overview, love and career guidance, advice, and the sexagenary year in force with its Ben Ming Nian flag. Content is fixed for a given date and rolls over at midnight, by default UTC.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Animal id, case-insensitive. One of rat, ox, tiger, rabbit, dragon, snake, horse, goat, monkey, rooster, dog, pig.
`date`	No	Reading date in YYYY-MM-DD format. Past and future dates are both supported, for editorial scheduling and backfill. Defaults to the current day 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
`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 day counts as current when date is omitted. Defaults to UTC, so the reading rolls over at 00:00 UTC each day. 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
`date`	Yes
`love`	Yes
`year`	Yes
`advice`	Yes
`animal`	Yes
`career`	Yes
`overview`	Yes
`dayPillar`	Yes
`benMingNian`	Yes
`energyRating`	Yes
`relationship`	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"
+    },
+    "animal": {
+      "properties": {
+        "branch": {
+          "type": "string"
+        },
+        "chinese": {
+          "type": "string"
+        },
+        "element": {
+          "type": "string"
+        },
+        "elementLocalized": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "nameLocalized": {
+          "type": "string"
+        },
+        "pinyin": {
+          "type": "string"
+        },
+        "polarity": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "name",
+        "chinese",
+        "pinyin",
+        "branch",
+        "element",
+        "polarity"
+      ],
+      "type": "object"
+    },
+    "benMingNian": {
+      "type": "boolean"
+    },
+    "career": {
+      "type": "string"
+    },
+    "date": {
+      "type": "string"
+    },
+    "dayPillar": {
+      "properties": {
+        "animal": {
+          "type": "string"
+        },
+        "branch": {
+          "type": "string"
+        },
+        "element": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "number": {
+          "type": "number"
+        },
+        "stem": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "number",
+        "stem",
+        "branch",
+        "animal",
+        "element"
+      ],
+      "type": "object"
+    },
+    "energyRating": {
+      "maximum": 10,
+      "minimum": 1,
+      "type": "number"
+    },
+    "love": {
+      "type": "string"
+    },
+    "overview": {
+      "type": "string"
+    },
+    "relationship": {
+      "type": "string"
+    },
+    "year": {
+      "properties": {
+        "animal": {
+          "type": "string"
+        },
+        "animalLocalized": {
+          "type": "string"
+        },
+        "note": {
+          "type": "string"
+        },
+        "pillar": {
+          "type": "string"
+        },
+        "relationship": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "pillar",
+        "animal",
+        "relationship",
+        "note"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "animal",
+    "date",
+    "dayPillar",
+    "relationship",
+    "energyRating",
+    "overview",
+    "love",
+    "career",
+    "advice",
+    "year",
+    "benMingNian"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantial behavioral context beyond that: the reading is generated from the day pillar's Earthly Branch and its classical relation to the requested sign, content is fixed for a given date, and it rolls over at midnight UTC by default. This prevents an agent from assuming the text is static, randomized, or mutable.

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?

The description is dense but every sentence earns its place: it states the action, the underlying method, the output fields, and the rollover behavior. It is front-loaded with the core purpose and does not include filler or repetition of schema details.

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?

Given the output schema exists and all parameters are fully described in the input schema, the description is complete enough for an agent to call the tool correctly. It adds the key conceptual context an agent cannot infer from schema alone: the day-pillar mechanism, the relation-based generation, and the deterministic rollover behavior.

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 schema already documents all five parameters with examples, defaults, formats, and enums. The description reinforces the roles of date and timezone ('fixed for a given date', 'by default UTC') but does not add meaningfully new parameter-level semantics beyond what the schema provides.

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 and resource: 'Get the daily reading for one Chinese zodiac animal.' It further differentiates itself from static or generic horoscope tools by explaining that content is built from the sexagenary day pillar rather than rotation of stock text, which makes its scope and method unmistakable.

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 clearly establishes when this tool is relevant: daily, per-animal, date-fixed readings that roll over at midnight UTC. However, it does not explicitly name alternatives or state when to use a sibling like get_chinese_astrology_zodiac_animals_id instead, so the routing guidance is implied rather than explicit.

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

All Chinese 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?