命盘 Mingpan

八字基礎排盤

bazi_basic

Calculate a Four Pillars (BaZi) chart from birth date, time, and gender, returning year, month, day, and hour stems/branches, hidden stems, Ten Gods, and optional timezone conversion.

Instructions

計算八字四柱（基礎排盤）。

輸入出生時間，返回由節氣與曆法精確推算的確定性結果：

年柱、月柱、日柱、時柱干支（含節氣月邊界、晚子時處理）及六十甲子納音
天干十神與藏干十神（各支藏干逐個標注，※為本氣）
十二長生（自坐）
命宮（三命通會子平起法）、胎元（月干進一支進三）
日柱旬空
公曆/農曆出生日期對照

時區說明：默認按北京時間排盤；海外出生者請提供 timezone 參數，系統將換算為北京時間後計算；可提供 longitude 做真太陽時校正。

定位說明：本工具只負責確定性排盤（干支、藏干、十神）。五行強弱、格局、用神、神煞等屬解讀層，無權威統一口徑，請由 AI 依據四柱自行分析。

大運/流年/流月/流日請使用對應列表工具。

Input Schema

TableJSON Schema

Name	Required	Description
`day`	Yes	日 1-31
`hour`	Yes	時 0-23
`name`	No	命主姓名（可選）
`year`	Yes	公曆年 1900-2100
`month`	Yes	月 1-12
`gender`	Yes	性別（影響大運順逆）
`minute`	No	分 0-59，默認 0
`isLunar`	No	輸入日期是否為農曆，默認公曆
`timezone`	No	IANA 時區名（如 America/New_York）。默認北京時間；設置後輸入時間按此時區換算為北京時間排盤。農曆輸入時忽略
`longitude`	No	出生地經度（真太陽時校正，可選）

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedv0.1.8Sep 30, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / day / description

Previous value: -"Birth day (1-31)"New value: +"日 1-31"

removedInput schema / properties / detail

Removed value: -{
-  "default": "standard",
-  "description": "Output detail level",
-  "enum": [
-    "simple",
-    "standard",
-    "detailed"
-  ],
-  "type": "string"
-}

removedInput schema / properties / gender / default
```
Removed value: -"male"
```

changedInput schema / properties / gender / description

Previous value: -"Gender for DaYun calculation direction"New value: +"性別（影響大運順逆）"

changedInput schema / properties / hour / description

Previous value: -"Birth hour in 24-hour format (0-23)"New value: +"時 0-23"

removedInput schema / properties / includeAnalysis

Removed value: -{
-  "default": true,
-  "description": "Include strength and pattern analysis",
-  "type": "boolean"
-}

removedInput schema / properties / includeDaYun

Removed value: -{
-  "default": true,
-  "description": "Include decade fortune (大運)",
-  "type": "boolean"
-}

changedInput schema / properties / isLunar / description

Previous value: -"Whether the input date is in lunar calendar (農曆). If true, will be converted to solar calendar internally."New value: +"輸入日期是否為農曆，默認公曆"

changedInput schema / properties / longitude / description

Previous value: -"Birth location longitude for true solar time adjustment"New value: +"出生地經度（真太陽時校正，可選）"

changedInput schema / properties / minute / description

Previous value: -"Birth minute (0-59)"New value: +"分 0-59，默認 0"

changedInput schema / properties / month / description

Previous value: -"Birth month (1-12)"New value: +"月 1-12"

addedInput schema / properties / name

Added value: +{
+  "description": "命主姓名（可選）",
+  "type": "string"
+}

removedInput schema / properties / targetYear

Removed value: -{
-  "description": "Calculate LiuNian (流年) for this specific year",
-  "type": "integer"
-}

addedInput schema / properties / timezone

Added value: +{
+  "description": "IANA 時區名（如 America/New_York）。默認北京時間；設置後輸入時間按此時區換算為北京時間排盤。農曆輸入時忽略",
+  "type": "string"
+}

changedInput schema / properties / year / description

Previous value: -"Birth year (e.g., 1990)"New value: +"公曆年 1900-2100"

changedInput schema / required

Previous value: -[
-  "year",
-  "month",
-  "day",
-  "hour"
-]New value: +[
+  "year",
+  "month",
+  "day",
+  "hour",
+  "gender"
+]

First observedv0.1.3Jun 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that results are deterministic, that timezone conversion to Beijing time occurs, that lunar input ignores timezone, and that the tool does not perform interpretation. It doesn't explicitly state read-only nature or absence of side effects, but for a排盤 calculation this is largely inferable from the description's scope.

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?

The description is front-loaded with purpose and organized with bullet points for outputs, timezone, positioning, and alternatives. It is appropriately detailed for a complex deterministic tool, though the output list is somewhat lengthy; every section still serves a clear purpose.

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?

No output schema exists, so the description must explain return values, which it does comprehensively (pillars, ten gods, etc.). It also covers timezone handling and scope boundaries. It is nearly complete for a 10-parameter tool, lacking only minor details like error behavior or input validation.

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 parameters. The description adds guidance that overseas users should provide timezone and that longitude enables true solar time correction, but this largely echoes the schema descriptions rather than adding new meaning beyond the structured fields.

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 and resource: 計算八字四柱（基礎排盤）. It clearly distinguishes this tool from siblings by stating that 大運/流年/流月/流日 use separate list tools, and that interpretation-layer analysis is not its job. An agent can identify it as the deterministic charting tool.

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

Usage Guidelines5/5

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

Explicit when-to-use is given: input birth time to get deterministic results. It names alternatives for 大運/流年 etc. and explicitly excludes interpretation (五行強弱, 格局, 用神, 神煞), telling the agent to handle those itself. This fully covers when and when-not to use.

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

Deploy Server

八字基礎排盤

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools