Chinese Astrology MCP Server by RoxyAPI

Find auspicious days - Chinese date selection API for weddings and openings

post_chinese_astrology_calendar_auspicious_days

Read-only

Search a date range for the days a chosen activity is favoured on, ranked by the jian chu day officer and filtered against a zodiac animal to protect. Every candidate day comes back with its officer, its pillars, its lunar date and the animal it clashes with, so a caller can show the reasoning rather than a bare verdict. The range is capped at 93 days, which is a quarter, because date selection is done inside a planning window rather than across a lifetime. Built for wedding planners, business opening tools, and moving and travel date pickers.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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.
`endDate`	Yes	Last date of the range to search, inclusive. The range may not exceed 93 days.
`activity`	Yes	Activity to choose a date for. One of wedding, travel, moving-house, opening-business, signing-contracts, construction, groundbreaking, burial, medical-treatment, praying. Matching folds case and punctuation, so moving-house and MOVING_HOUSE both resolve.
`startDate`	Yes	First date of the range to search, inclusive.
`avoidAnimal`	No	Zodiac animal to protect. Days that clash with this animal are dropped from the results, which is how a date is chosen around the people attending rather than in the abstract. One of rat, ox, tiger, rabbit, dragon, snake, horse, goat, monkey, rooster, dog, pig.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`days`	Yes
`total`	Yes
`endDate`	Yes
`activity`	Yes
`startDate`	Yes
`avoidAnimal`	No
`daysSearched`	Yes
`activityLabel`	Yes
`avoidAnimalLocalized`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "activity": {
+      "type": "string"
+    },
+    "activityLabel": {
+      "type": "string"
+    },
+    "avoidAnimal": {
+      "type": "string"
+    },
+    "avoidAnimalLocalized": {
+      "type": "string"
+    },
+    "days": {
+      "items": {
+        "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"
+      },
+      "type": "array"
+    },
+    "daysSearched": {
+      "type": "number"
+    },
+    "endDate": {
+      "type": "string"
+    },
+    "startDate": {
+      "type": "string"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "activity",
+    "activityLabel",
+    "startDate",
+    "endDate",
+    "daysSearched",
+    "total",
+    "days"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.3/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. Description adds the substantive behavior: returns ranked results with officer, pillars, lunar date, and clash details, and enforces the 93-day range cap. Also notes the compact parameter's token savings, but the core behavioral disclosure is strong.

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?

Four sentences that are dense but efficient. Front-loads the core purpose (search + ranking), then adds output details and constraints. No fluff; every sentence earns its place.

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 rich annotations, complete schema, and output schema presence, the description covers all necessary context: what it does, how results are presented, the range constraint, and target use cases. Nothing critical is missing for an agent to call 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%, so the schema already documents all six parameters. The description adds context for the activity and avoidAnimal (why they matter) and the range cap, but doesn't go beyond the schema for lang and compact. 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?

States a specific verb (search), resource (date range for a chosen activity), and key filtering criteria (jian chu day officer, zodiac animal). Distinguishes from siblings by focusing on auspicious day search rather than single-day, monthly, or year-based calendar 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?

Clear that it's for date selection within a planning window, with explicit 93-day cap. Implicitly positioned against siblings (single days, monthly, solar terms), but no explicit 'when not to use' or comparison to alternative tools.

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?