Chinese Astrology MCP Server by RoxyAPI

Get a month of almanac days - Chinese calendar month view API

get_chinese_astrology_calendar_monthly

Read-only

Return every day of one Gregorian month of the Chinese almanac with its lunisolar date, its three pillars, its day officer, its lunar mansion and its clash animal, plus the solar terms that fall inside the month. This is the month view a calendar widget renders in one call rather than thirty one. Omit the year and month to get the month in progress. Built for calendar UIs, almanac pages, and planning tools that show a whole month at a glance.

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
`year`	No	Gregorian year, 1900 to 2100. Defaults to the current UTC year when omitted, together with month.
`month`	No	Gregorian month, 1 to 12. Defaults to the current UTC month when omitted, together with year.
`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
`days`	Yes
`year`	Yes
`month`	Yes
`total`	Yes
`solarTerms`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "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"
+    },
+    "month": {
+      "type": "number"
+    },
+    "solarTerms": {
+      "items": {
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "instantUtc": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "type",
+          "date",
+          "instantUtc"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    },
+    "year": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "year",
+    "month",
+    "total",
+    "solarTerms",
+    "days"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedSep 19, 2026
- changedInput schema / properties / month / type
```
Previous value: -"number"New value: +"integer"
```
- changedInput schema / properties / year / type
```
Previous value: -"number"New value: +"integer"
```
Changed4 schema fields changedSep 18, 2026
- addedInput schema / properties / month / maximum
```
Added value: +12
```
- addedInput schema / properties / month / minimum
```
Added value: +1
```
- addedInput schema / properties / year / maximum
```
Added value: +2100
```
- addedInput schema / properties / year / minimum
```
Added value: +1900
```
First observedSep 1, 2026

TDQS

A4.2/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, and the description adds useful behavior beyond that: it returns every day in the month, includes solar terms falling in the month, and defaults to the month in progress when year and month are omitted. No hidden destructive or state-changing behavior is suggested.

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 front-loaded with the core return behavior and is appropriately sized. The last sentence about being built for calendar UIs and almanac pages is somewhat redundant with the earlier month-view framing, but it does not waste much space.

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 that an output schema exists and annotations cover the safety profile, the description is complete for invocation: it defines scope, default behavior, target use cases, and distinguishes the month view from the day-level alternative. No critical information needed to select or call the tool is missing.

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 four parameters. The description's only parameter-related statement, 'Omit the year and month to get the month in progress,' largely repeats the schema's stated defaults, adding no new semantic value beyond what is already structured.

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 states a specific verb and resource: 'Return every day of one Gregorian month of the Chinese almanac' and enumerates the included data fields. It clearly differentiates itself from the single-day and solar-terms siblings by framing itself as the month view rendered in one call rather than thirty one.

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 gives clear context: it is built for calendar UIs, almanac pages, and planning tools that show a whole month at a glance, and it contrasts with making thirty-one separate calls. It does not explicitly name the day-level sibling as the alternative, so it falls short of the strongest explicit when/when-not guidance.

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?