Skip to main content
Glama
openfate-ai

OpenFate Bazi MCP

Official

Calculate Bazi Chart

calculate_bazi_chart
Read-onlyIdempotent

Calculate a deterministic Bazi/Four Pillars chart using birth year, month, day, gender, and optional time details, with True Solar Time correction, Day Master, Da Yun cycles, and branch interactions.

Instructions

Calculate a deterministic OpenFate Bazi/Four Pillars chart with True Solar Time correction, Day Master, Da Yun cycles, and branch interactions. For best accuracy, pass longitude plus timezone or timezoneId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayYesBirth day, 1-31.
hourNoBirth hour in local civil time, 0-23. Omit when birth time is unknown.
yearYesBirth year. Use the lunar year when calendarType is lunar.
monthYesBirth month, 1-12.
genderYesBirth gender used for Da Yun direction.
minuteNoBirth minute in local civil time.
timezoneNoUTC offset in hours for the birth clock time, such as 8 for China or -5 for US Eastern Standard Time.
dstOffsetNoDaylight saving offset in hours to remove from civil clock time. Use 1 for one-hour DST.
longitudeNoBirthplace longitude in decimal degrees. Enables true solar time correction.
timezoneIdNoOptional IANA timezone ID, such as Asia/Shanghai or America/New_York.
isLeapMonthNoWhether the lunar input month is a leap month. Used only when calendarType is lunar.
calendarTypeNoInput calendar type.solar
dayBoundaryModeNoDay-change rule. ZI_HOUR_23 means 23:00 starts the next day pillar.ZI_HOUR_23
enableTrueSolarTimeNoApply true solar time when longitude and timezone data are available.
Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent. The description adds that the calculation is deterministic and uses true solar time correction, providing extra context beyond annotations. No contradictions.

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?

Two sentences: first states purpose, second gives guidance. No wasted words, highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the tool is complex with 14 parameters, the description covers purpose and key features. However, it does not describe the output format or list expected return fields, which is a gap given the absence of an output schema.

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 parameters. The description adds a tip about accuracy but does not further explain parameter meanings or relationships, so it adds minimal value.

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?

The description clearly states the tool calculates a Bazi/Four Pillars chart with specific features (true solar time, Day Master, Da Yun cycles, branch interactions). It does not explicitly distinguish from sibling tools, but the purpose is sufficiently clear.

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 description advises passing longitude and timezone/timezoneId for best accuracy, providing some guidance. However, it lacks explicit when-to-use vs alternatives or conditions under which this tool should be preferred over siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/openfate-ai/bazi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server