Skip to main content
Glama

Chinese Astrology MCP Server by RoxyAPI

Calculate BaZi annual forecast - Liu Nian yearly pillar API

post_chinese_astrology_bazi_annual_forecast
Read-only

Read one Gregorian year against a natal BaZi chart. Returns the annual pillar for that year, the Ten God relation its stem holds to the natal Day Master, the same reading for the hidden stem of its branch, how the annual branch stands to the natal year branch including the ben ming nian return of the birth animal, and every combination, clash, harm and punishment the annual pillar forms with each of the four natal pillars. Built for yearly horoscope features, timing tools, and agents that need a year read against a specific chart rather than against an animal sign.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesBirth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.
langNoResponse 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
timeYesBirth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.
yearYesGregorian year to read against the natal chart. The annual pillar for that year is resolved under the same year boundary the request selected, so a li-chun reading and a lunar-new-year reading of the same calendar year can differ.
compactNoSet 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.
latitudeNoBirth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.
timezoneYesIANA name (e.g. "America/New_York", "Europe/London", "UTC"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00", "+01:00"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.
hourClockNoWhich clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. "clock" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. "local-mean" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. "solar" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need "longitude" in the request and return 400 without it.clock
longitudeNoBirth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is "local-mean" or "solar", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is "clock".
dayBoundaryNoWhich instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. "midnight" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. "early-zi" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. "split-zi" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.split-zi
yearBoundaryNoWhich instant starts the sexagenary YEAR. "li-chun" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. "lunar-new-year" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.li-chun

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYes
animalYes
tenGodYes
summaryYes
birthDataYes
benMingNianYes
conventionsYes
annualPillarYes
branchTenGodYes
interactionsYes
animalLocalizedNo
yearBranchRelationYes
yearBranchRelationMeaningYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / year / maximum
      Previous value: -2100New value: +2649
    • changedInput schema / properties / year / minimum
      Previous value: -1900New value: +1551
  2. Changed1 schema field changed
    • changedInput schema / properties / hourClock / description
      Previous value: -"Which clock the HOUR branch is read from. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it."New value: +"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "animal": {
      +      "type": "string"
      +    },
      +    "animalLocalized": {
      +      "type": "string"
      +    },
      +    "annualPillar": {
      +      "properties": {
      +        "branch": {
      +          "properties": {
      +            "animal": {
      +              "type": "string"
      +            },
      +            "animalLocalized": {
      +              "type": "string"
      +            },
      +            "chinese": {
      +              "type": "string"
      +            },
      +            "element": {
      +              "type": "string"
      +            },
      +            "elementLocalized": {
      +              "type": "string"
      +            },
      +            "id": {
      +              "type": "string"
      +            },
      +            "pinyin": {
      +              "type": "string"
      +            },
      +            "polarity": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "id",
      +            "chinese",
      +            "pinyin",
      +            "animal",
      +            "element",
      +            "polarity"
      +          ],
      +          "type": "object"
      +        },
      +        "id": {
      +          "type": "string"
      +        },
      +        "naYin": {
      +          "type": "string"
      +        },
      +        "naYinChinese": {
      +          "type": "string"
      +        },
      +        "number": {
      +          "type": "number"
      +        },
      +        "stem": {
      +          "properties": {
      +            "chinese": {
      +              "type": "string"
      +            },
      +            "element": {
      +              "type": "string"
      +            },
      +            "elementLocalized": {
      +              "type": "string"
      +            },
      +            "id": {
      +              "type": "string"
      +            },
      +            "pinyin": {
      +              "type": "string"
      +            },
      +            "polarity": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "id",
      +            "chinese",
      +            "pinyin",
      +            "element",
      +            "polarity"
      +          ],
      +          "type": "object"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "number",
      +        "stem",
      +        "branch",
      +        "naYin",
      +        "naYinChinese"
      +      ],
      +      "type": "object"
      +    },
      +    "benMingNian": {
      +      "type": "boolean"
      +    },
      +    "birthData": {
      +      "properties": {
      +        "date": {
      +          "format": "date",
      +          "type": "string"
      +        },
      +        "latitude": {
      +          "default": 0,
      +          "maximum": 90,
      +          "minimum": -90,
      +          "type": "number"
      +        },
      +        "longitude": {
      +          "maximum": 180,
      +          "minimum": -180,
      +          "type": "number"
      +        },
      +        "time": {
      +          "format": "time",
      +          "type": "string"
      +        },
      +        "timezone": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "date",
      +        "time",
      +        "timezone"
      +      ],
      +      "type": "object"
      +    },
      +    "branchTenGod": {
      +      "properties": {
      +        "category": {
      +          "type": "string"
      +        },
      +        "chinese": {
      +          "type": "string"
      +        },
      +        "id": {
      +          "type": "string"
      +        },
      +        "keynote": {
      +          "type": "string"
      +        },
      +        "name": {
      +          "type": "string"
      +        },
      +        "nameLocalized": {
      +          "type": "string"
      +        },
      +        "pinyin": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "name",
      +        "chinese",
      +        "pinyin",
      +        "category",
      +        "keynote"
      +      ],
      +      "type": "object"
      +    },
      +    "conventions": {
      +      "properties": {
      +        "dayBoundary": {
      +          "enum": [
      +            "split-zi",
      +            "midnight",
      +            "early-zi"
      +          ],
      +          "type": "string"
      +        },
      +        "hourClock": {
      +          "enum": [
      +            "clock",
      +            "local-mean",
      +            "solar"
      +          ],
      +          "type": "string"
      +        },
      +        "yearBoundary": {
      +          "enum": [
      +            "li-chun",
      +            "lunar-new-year"
      +          ],
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "dayBoundary",
      +        "yearBoundary",
      +        "hourClock"
      +      ],
      +      "type": "object"
      +    },
      +    "interactions": {
      +      "items": {
      +        "properties": {
      +          "chinese": {
      +            "type": "string"
      +          },
      +          "complete": {
      +            "type": "boolean"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "meaning": {
      +            "type": "string"
      +          },
      +          "members": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "pinyin": {
      +            "type": "string"
      +          },
      +          "positions": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "quality": {
      +            "type": "string"
      +          },
      +          "transformsTo": {
      +            "type": "string"
      +          },
      +          "type": {
      +            "type": "string"
      +          },
      +          "variety": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "type",
      +          "id",
      +          "chinese",
      +          "pinyin",
      +          "quality",
      +          "positions",
      +          "members",
      +          "meaning"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "summary": {
      +      "type": "string"
      +    },
      +    "tenGod": {
      +      "properties": {
      +        "category": {
      +          "type": "string"
      +        },
      +        "chinese": {
      +          "type": "string"
      +        },
      +        "id": {
      +          "type": "string"
      +        },
      +        "keynote": {
      +          "type": "string"
      +        },
      +        "name": {
      +          "type": "string"
      +        },
      +        "nameLocalized": {
      +          "type": "string"
      +        },
      +        "pinyin": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "name",
      +        "chinese",
      +        "pinyin",
      +        "category",
      +        "keynote"
      +      ],
      +      "type": "object"
      +    },
      +    "year": {
      +      "type": "number"
      +    },
      +    "yearBranchRelation": {
      +      "type": "string"
      +    },
      +    "yearBranchRelationMeaning": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "birthData",
      +    "conventions",
      +    "year",
      +    "annualPillar",
      +    "animal",
      +    "tenGod",
      +    "branchTenGod",
      +    "yearBranchRelation",
      +    "benMingNian",
      +    "yearBranchRelationMeaning",
      +    "interactions",
      +    "summary"
      +  ],
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error."New value: +"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error."
  5. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish this is a safe read (readOnlyHint=true, destructiveHint=false), and the description adds substantive behavioral detail about the computed outputs and the caveats around year-boundary resolution. It stops short of noting latency, rate limits, or error behaviour beyond what the schema covers.

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?

Two sentences, front-loaded with the action and then the return payload; the long enumeration of outputs is dense but each item is decision-relevant. Slightly heavy for a definition whose schema already documents inputs.

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 11 parameters at full schema coverage and an output schema present, the description need not re-document fields; it still usefully frames the domain (natal chart vs animal sign) and output shape. Nothing critical is missing, though explicit sibling routing would round it out.

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 every parameter already carries a rich, self-contained description (timezone resolution, dayBoundary, yearBoundary, hourClock). The description text itself contributes essentially no parameter guidance, so the baseline 3 applies rather than a penalty.

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 first sentence states a specific verb and resource ('Read one Gregorian year against a natal BaZi chart') and the rest enumerates exactly what is returned (annual pillar, Ten God relation, branch relations, combinations/clashes/harms/punishments). It also differentiates from the zodiac-sign siblings by noting it reads against 'a specific chart rather than against an animal sign'.

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?

It gives clear intended contexts ('yearly horoscope features, timing tools') and one exclusion (not an animal-sign reading), which routes the agent away from the zodiac_sign tools. It does not, however, name or contrast with the closest sibling, post_chinese_astrology_bazi_chart, or state prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources