Skip to main content
Glama

FateSign BaZi

Calculate a BaZi chart

calculate_bazi_chart
Read-onlyIdempotent

Calculates a BaZi (Four Pillars of Destiny, 八字 / 四柱推命 / 사주) chart for one person from their birth details, using FateSign's calendar engine with time zones, historical daylight saving, True Solar Time and solar-term boundaries. Returns the four pillars with hidden stems, Ten Gods, Twelve Stages, Na Yin and Shen Sha; the Five Elements balance, seasonal strength and relations; the luck cycles (Da Yun), the annual pillars of the current cycle and the monthly pillars of focus_year; the matched birthplace and time corrections; and links to FateSign pages in the requested language.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "gender": "<gender>",
      "birth_date": "<birth_date>"
    },
    "name": "calculate_bazi_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the labels in the result. Match the user's language.en
genderYesSets the direction of the luck cycles.
calendarNoUse lunar only when the user gives a Chinese lunar-calendar date.solar
timezoneNoIANA time zone such as Asia/Shanghai. Only when the birthplace is unknown; True Solar Time is then not applied.
birth_dateYesBirth date as YYYY-MM-DD. With calendar=lunar this is the lunar year, month and day.
birth_timeNoLocal clock time at birth, 24-hour HH:MM. null when the user does not know it (the hour pillar is then omitted). Do not adjust it for daylight saving or solar time.
focus_yearNoYear for the annual and monthly pillars. Defaults to the current year.
birth_placeNoBirth city and country, e.g. 'Osaka, Japan'. Used for the time zone, daylight saving and True Solar Time. Required unless timezone is given.
lunar_leap_monthNoTrue when a lunar date falls in a leap month.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the engine handles time zones, historical daylight saving, True Solar Time and solar-term boundaries, and it explains that missing birth time omits the hour pillar and that the birthplace is "matched". It stops short of stating what happens on a failed birthplace match or whether results are cached, which keeps it off a 5.

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?

It is a single long sentence, but it is front-loaded with purpose before the return-value enumeration, so a reader gets the point in the first clause. The dense semicolon-separated list of returned components is long yet earns its place because no output schema exists to carry that information.

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 9-parameter calculation tool with no output schema, this covers the essentials: what goes in, what comes back, and the special-case handling of missing birth time and unknown birthplace. What is missing is failure behavior and any note on cost or latency, which for a non-trivial calendar computation an agent might want to know.

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 every one of the nine parameters is already documented with defaults, patterns and enums - the baseline of 3 therefore applies. The description adds only indirect meaning (birthplace drives time corrections, focus_year drives monthly pillars) beyond what the schema fields state directly.

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 opens with a specific verb and resource - "Calculates a BaZi (Four Pillars of Destiny...) chart for one person from their birth details" - and then enumerates exactly what the tool produces (pillars, Five Elements, Da Yun, annual/monthly pillars, birthplace corrections). There are no sibling tools to differentiate from, but the scope is unambiguous without opening the schema.

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?

Usage guidance exists but is scattered in the schema descriptions rather than the tool description itself - e.g. timezone "Only when the birthplace is unknown", calendar "Use lunar only when the user gives a Chinese lunar-calendar date". The description proper says only that it works "for one person from their birth details", which implies but never states the when/when-not conditions. An agent gets the routing guidance only by reading parameter docs.

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