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

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description reveals meaningful behavior: content is derived from the actual sexagenary day pillar, uses six classical relations, is fixed for a date, and rolls over at midnight UTC. It also lists what the response contains. This is substantial value beyond annotation data.

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 well organized: what it does, how it is computed, what it returns, and temporal behavior. Every sentence contributes information, and the key purpose is front-loaded.

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 sufficiently enumerates the returned fields and key behavior such as date rollover and timezone handling. Slight gaps remain in describing exact output shape and edge cases, but the schema covers the inputs and the description is otherwise complete for invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All parameters are already well described in the schema, so the baseline is 3. The description adds useful context by explaining that content is date-fixed and rolls over at midnight and that UTC is the default, reinforcing the date/timezone semantics beyond the schema.

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?

States a specific verb and resource: get one Chinese zodiac animal's daily reading. It also distinguishes the tool's mechanism from stock-text rotations and names the exact returned content, making it clearly different from sibling tools.

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?

Clearly frames the tool as a daily, single-sign, sexagenary-based forecast and notes the day/timestamp rollover behavior. It does not explicitly name alternatives or exclusions relative to sibling bazi or calendar tools, but the scope is evident from the description.

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

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

A4.3/5.0

Disambiguation5/5

Each tool targets a distinct resource and action: single-day almanac, month view, solar terms, lunar conversion, auspicious day search, zodiac list/profile/compatibility/daily, and BaZi chart/forecast/compatibility/day-master/luck-pillars. Even adjacent calendar and zodiac tools are separated by clear input/output differences, so an agent is unlikely to misselect.

Naming Consistency4/5

All names are snake_case with a consistent get_/post_ prefix, a chinese_astrology domain segment, and predictable subdomain grouping for calendar, zodiac, and bazi. Minor inconsistencies remain, such as zodiac_animals_id versus zodiac_id_daily and calendar_day_date versus calendar_monthly, but the overall pattern is readable and systematic.

Tool Count4/5

16 tools is one above the typical 3–15 sweet spot, but the server covers three distinct subdomains: almanac/calendar, zodiac, and BaZi. Each tool maps to a concrete feature, so the count feels slightly broad rather than bloated, though a few reference lookups could theoretically be consolidated.

Completeness5/5

The tool surface covers the main Chinese astrology workflows end to end: calendar/almanac, lunar conversion, solar terms, auspicious day selection, zodiac profiles, compatibility, daily readings, BaZi chart calculation, day master analysis, luck pillars, annual forecasts, and two-chart compatibility. There are no obvious dead ends or missing operations for the stated domain.

Resources

Need Help?