Skip to main content
Glama

Chinese Astrology MCP Server by RoxyAPI

Calculate Day Master strength - BaZi favorable element API

post_chinese_astrology_bazi_day_master
Read-only

Assess how well the Day Master is supported by the rest of a BaZi chart, and which of the five elements help it. Uses the classical three-factor method: whether the birth month season backs the Day Master element, whether any branch stores a root for it, and whether the other stems and the branches outside the month help or spend it. Returns the verdict, an auditable score with each factor contribution, the seasonal state, the root count, the element headcount, and the favorable and unfavorable element lists that follow from the verdict. Built for chart readers, remedy features, and agents that need the usable half of a Four Pillars reading.

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.
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
scoreYes
factorsYes
summaryYes
verdictYes
birthDataYes
dayMasterYes
rootCountYes
conventionsYes
fiveElementsYes
seasonalStateYes
favorableElementsYes
unfavorableElementsYes
seasonalStateChineseYes
seasonalStateMeaningYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "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"
      +    },
      +    "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"
      +    },
      +    "dayMaster": {
      +      "properties": {
      +        "chinese": {
      +          "type": "string"
      +        },
      +        "element": {
      +          "type": "string"
      +        },
      +        "elementLocalized": {
      +          "type": "string"
      +        },
      +        "nature": {
      +          "type": "string"
      +        },
      +        "pinyin": {
      +          "type": "string"
      +        },
      +        "polarity": {
      +          "type": "string"
      +        },
      +        "stem": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "stem",
      +        "chinese",
      +        "pinyin",
      +        "element",
      +        "polarity",
      +        "nature"
      +      ],
      +      "type": "object"
      +    },
      +    "factors": {
      +      "items": {
      +        "properties": {
      +          "chinese": {
      +            "type": "string"
      +          },
      +          "contribution": {
      +            "type": "number"
      +          },
      +          "detail": {
      +            "type": "string"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "pinyin": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "name",
      +          "chinese",
      +          "pinyin",
      +          "contribution",
      +          "detail"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "favorableElements": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "fiveElements": {
      +      "items": {
      +        "properties": {
      +          "count": {
      +            "type": "number"
      +          },
      +          "element": {
      +            "type": "string"
      +          },
      +          "elementLocalized": {
      +            "type": "string"
      +          },
      +          "level": {
      +            "type": "string"
      +          },
      +          "reading": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "element",
      +          "count",
      +          "level",
      +          "reading"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "rootCount": {
      +      "type": "number"
      +    },
      +    "score": {
      +      "type": "number"
      +    },
      +    "seasonalState": {
      +      "type": "string"
      +    },
      +    "seasonalStateChinese": {
      +      "type": "string"
      +    },
      +    "seasonalStateMeaning": {
      +      "type": "string"
      +    },
      +    "summary": {
      +      "type": "string"
      +    },
      +    "unfavorableElements": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "verdict": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "birthData",
      +    "conventions",
      +    "dayMaster",
      +    "verdict",
      +    "score",
      +    "seasonalState",
      +    "seasonalStateChinese",
      +    "seasonalStateMeaning",
      +    "rootCount",
      +    "factors",
      +    "favorableElements",
      +    "unfavorableElements",
      +    "fiveElements",
      +    "summary"
      +  ],
      +  "type": "object"
      +}
  3. 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."
  4. First observed

TDQS

A3.7/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, so the safety bar is low. The description goes further by disclosing the computation method (season, root, other stems/branches) and enumerating the verdict, per-factor score contributions, seasonal state, root count, and element lists that come back.

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 purpose and method before the return contents and audience. Dense but every clause carries information; the trailing audience sentence is the only mildly expendable part.

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?

For a ten-parameter domain tool with an output schema and fully documented schema fields, the description is adequate: it explains what is computed and what is returned. It relies entirely on the schema for parameter caveats, which is acceptable given 100% coverage.

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 ten parameters in depth. The description adds no parameter-level guidance (no mention of date/time/timezone, hourClock, dayBoundary, or the longitude dependency), so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource: assess Day Master support and identify favorable/unfavorable elements, with the three-factor method spelled out. It is clearly a sub-analysis of a BaZi reading rather than a full chart, but it never names the sibling tools (e.g. post_chinese_astrology_bazi_chart) that would distinguish it explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The audience line ('built for chart readers, remedy features, and agents that need the usable half of a Four Pillars reading') implies when this is useful, but there is no explicit when-to-use/when-not and no routing to alternatives among the many bazi siblings.

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