Chinese Astrology MCP Server by RoxyAPI

Get the almanac for a day - Tong Shu API with day officers and mansions

get_chinese_astrology_calendar_day_date

Read-only

Return the full almanac reading of one day: its lunisolar date, the year, month and day pillars with their Na Yin, the day officer from the twelve jian chu sequence, the lunar mansion on duty, the zodiac animal the day clashes with, and the activities the officer favours or opposes. The day officer is the layer a printed almanac reaches its verdict from first, and the response says exactly what it rules on rather than reducing the day to a single score. The year and month pillars here are attributed by whole days, which is what an almanac prints: the day a solar term falls on belongs to the new period for its whole length, however late in the day the term arrives. Built for date pickers, daily calendar widgets, and wedding or opening date tools.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes	Gregorian date in YYYY-MM-DD format, evaluated at the reference meridian. Years 1900 to 2100.
`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
`date`	Yes
`lunar`	Yes
`avoids`	Yes
`favours`	Yes
`mansion`	Yes
`dayPillar`	Yes
`dayOfficer`	Yes
`yearPillar`	Yes
`clashAnimal`	Yes
`monthPillar`	Yes
`clashAnimalLocalized`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "avoids": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "clashAnimal": {
+      "type": "string"
+    },
+    "clashAnimalLocalized": {
+      "type": "string"
+    },
+    "date": {
+      "type": "string"
+    },
+    "dayOfficer": {
+      "properties": {
+        "chinese": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "meaning": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "nameLocalized": {
+          "type": "string"
+        },
+        "pinyin": {
+          "type": "string"
+        },
+        "quality": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "name",
+        "chinese",
+        "pinyin",
+        "quality",
+        "meaning"
+      ],
+      "type": "object"
+    },
+    "dayPillar": {
+      "properties": {
+        "branch": {
+          "type": "string"
+        },
+        "chinese": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "naYin": {
+          "type": "string"
+        },
+        "naYinElement": {
+          "type": "string"
+        },
+        "number": {
+          "type": "number"
+        },
+        "stem": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "number",
+        "stem",
+        "branch",
+        "chinese",
+        "naYin",
+        "naYinElement"
+      ],
+      "type": "object"
+    },
+    "favours": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "lunar": {
+      "properties": {
+        "date": {
+          "type": "string"
+        },
+        "day": {
+          "type": "number"
+        },
+        "isLeapMonth": {
+          "type": "boolean"
+        },
+        "month": {
+          "type": "number"
+        },
+        "monthLength": {
+          "type": "number"
+        },
+        "year": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "year",
+        "month",
+        "day",
+        "isLeapMonth",
+        "monthLength",
+        "date"
+      ],
+      "type": "object"
+    },
+    "mansion": {
+      "properties": {
+        "animal": {
+          "type": "string"
+        },
+        "animalLocalized": {
+          "type": "string"
+        },
+        "chinese": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "nameLocalized": {
+          "type": "string"
+        },
+        "number": {
+          "type": "number"
+        },
+        "palace": {
+          "type": "string"
+        },
+        "pinyin": {
+          "type": "string"
+        },
+        "planet": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "number",
+        "name",
+        "chinese",
+        "pinyin",
+        "palace",
+        "planet",
+        "animal"
+      ],
+      "type": "object"
+    },
+    "monthPillar": {
+      "properties": {
+        "branch": {
+          "type": "string"
+        },
+        "chinese": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "naYin": {
+          "type": "string"
+        },
+        "naYinElement": {
+          "type": "string"
+        },
+        "number": {
+          "type": "number"
+        },
+        "stem": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "number",
+        "stem",
+        "branch",
+        "chinese",
+        "naYin",
+        "naYinElement"
+      ],
+      "type": "object"
+    },
+    "yearPillar": {
+      "properties": {
+        "branch": {
+          "type": "string"
+        },
+        "chinese": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "naYin": {
+          "type": "string"
+        },
+        "naYinElement": {
+          "type": "string"
+        },
+        "number": {
+          "type": "number"
+        },
+        "stem": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "number",
+        "stem",
+        "branch",
+        "chinese",
+        "naYin",
+        "naYinElement"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "date",
+    "lunar",
+    "yearPillar",
+    "monthPillar",
+    "dayPillar",
+    "dayOfficer",
+    "mansion",
+    "clashAnimal",
+    "favours",
+    "avoids"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 18, 2026
- addedInput schema / properties / date / format
```
Added value: +"date"
```
First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Given that annotations already declare readOnlyHint=true and destructiveHint=false, the safety profile is covered. The description adds genuinely valuable behavior beyond that: it discloses that year/month pillars are attributed by whole days regardless of when a solar term arrives, and that the response 'says exactly what it rules on rather than reducing the day to a single score' — both non-obvious behaviors an agent needs to interpret results correctly.

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

Conciseness4/5

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

The description is four dense sentences that each earn their place: return contents, the day officer's interpretive role, the pillar-attribution rule, and target use cases. It is front-loaded with the output list and contains no filler, though it runs slightly long due to the inherent complexity of the domain.

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 an output schema present, annotations covering safety, and 100% parameter coverage, the description only needs to resolve domain ambiguities — and it does, explaining the solar-term attribution rule and the day officer's primacy. The tool is complex, but the only notable gap is the absence of explicit sibling routing; everything an agent needs to invoke it correctly is otherwise present.

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%, and the schema already documents date format, the lang enum with fallback behavior, and the compact columnar shape. The description adds no parameter-specific semantics beyond what the schema states, so the baseline of 3 applies.

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 ('Return the full almanac reading of one day') and enumerates the exact contents (lunisolar date, pillars with Na Yin, day officer, lunar mansion, clash animal, favoured/opposed activities). The 'one day' scope clearly differentiates it from the monthly and solar-terms-year calendar siblings in the tool list.

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 closing sentence states concrete use cases: 'Built for date pickers, daily calendar widgets, and wedding or opening date tools.' This gives clear application context, but the description never names alternatives or states when not to use this tool (e.g., for a monthly range), so explicit exclusion guidance is absent.

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?