Chinese Astrology MCP Server by RoxyAPI

Convert lunar and Gregorian dates - Chinese lunisolar calendar API

post_chinese_astrology_calendar_lunar_date

Read-only

Convert a Gregorian date to the Chinese lunisolar calendar or convert a lunar date back, in one endpoint. The calendar is computed at the UTC+8 reference meridian with the month containing the winter solstice fixed as month 11 and the leap month placed as the first month of the cycle carrying no major solar term, so a lunar date is the same worldwide rather than shifting with the caller timezone. The response reports the length of the lunar month, whether the date sits in a leap month, and which month the year doubles if any. Built for festival calendars, birthday features that follow the lunar date, and any app that has to survive a leap month without shifting every date after it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Gregorian date to convert to the lunisolar calendar. Send this OR the lunar fields, never both.
`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.
`lunarDay`	No	Day of the lunar month, 1 to 30. Requires lunarYear and lunarMonth.
`lunarYear`	No	Lunisolar year to convert back to a Gregorian date. Requires lunarMonth and lunarDay.
`lunarMonth`	No	Lunar month, 1 to 12. Requires lunarYear and lunarDay.
`isLeapMonth`	No	Set true to address the leap repetition of lunarMonth rather than the first pass. Requesting a leap month a year does not have returns 400.

TDQS

A4.5/5.0

Behavior5/5

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

With readOnlyHint=true and destructiveHint=false already declared, the description adds substantial non-obvious behavioral context: UTC+8 reference meridian, winter-solstice month-11 rule, leap-month placement rules, timezone invariance, and exactly what the response reports. This goes well beyond the annotations.

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 four sentences with no filler. It front-loads the core conversion purpose, then efficiently adds computational rules, response contents, and use cases in descending order of importance.

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?

The description covers the tool's purpose, timezone behavior, leap-month behavior, response contents, and suitable applications. Since there is no output schema, the response-content summary is valuable, and the input schema plus annotations complete the picture for correct invocation.

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 seven parameters including mutual exclusivity, ranges, defaults, and dependencies. The description adds high-level conversion semantics but does not need to repeat parameter-specific details; the baseline of 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?

The description states a specific verb (Convert), resource (Chinese lunisolar calendar), and both conversion directions (Gregorian to lunar and lunar back to Gregorian), which makes the tool's purpose unmistakable. It also distinguishes itself from sibling calendar tools by emphasizing that both conversions happen in one endpoint.

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 concrete use cases—festival calendars, lunar-date birthdays, and apps that must handle leap months—so an agent can recognize when to choose this tool. It does not explicitly name alternative sibling endpoints or say when not to use it, leaving room for inference.

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?