Skip to main content
Glama
ChesterRa

命盘 Mingpan

by ChesterRa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

奇門遁甲排盤

qimen_basic

Generate a Qimen Dunjia astrological chart from date and time. Returns nine palaces, eight gates, nine stars, eight gods, hour/day stems, and pattern judgments for divination and decision-making.

Instructions

奇門遁甲排盤（基礎排盤）。

奇門遁甲是中國古代三式之一，與大六壬、太乙神數並稱，用於預測和決策。

輸入時間信息，返回完整的奇門盤面：

  • 陰陽遁和局數（根據節氣判定）

  • 九宮布局（地盤干、天盤干）

  • 八門飛布（休、生、傷、杜、景、死、驚、開）

  • 九星飛布（天蓬、天芮、天沖、天輔、天禽、天心、天柱、天任、天英）

  • 八神排布（值符、螣蛇、太陰、六合、白虎、玄武、九地、九天）

  • 旬首信息（符頭、值符星、值使門、空亡）

  • 日干/時干落宮

  • 格局判斷（吉格/凶格約20-30種）

支持選項：

  • 盤類型：時盤（默認）、日盤、月盤、年盤

  • 盤式：轉盤（默認，遵循《神奇之門》）或飛盤

  • 置閏法：拆補法（默認）或茅山法

盤類型說明：

  • 時盤：以時辰為主導，適用於即時預測

  • 日盤：以日干支為主導，適用於當日吉凶

  • 月盤：以月干支為主導，適用於月度運勢

  • 年盤：以年干支為主導，適用於年度規劃

盤式說明：

  • 轉盤：天盤、八門、九星按物理方向旋轉（《神奇之門》派）

  • 飛盤：天盤、八門、九星按宮位數字飛布（傳統飛宮法）

輸出為 Markdown 格式，含 ASCII 九宮格，便於 AI 分析解讀。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayYes日 1-31
hourYes時 0-23
yearYes公曆年 1900-2100
monthYes月 1-12
minuteNo分 0-59，默認 0
isLunarNo輸入日期是否為農曆，默認公曆
panTypeNo盤類型：时盘（默認）、日盘、月盘、年盘时盘
panStyleNo盤式：转盘（默認，遵循《神奇之門》）或飞盘转盘
timezoneNoIANA 時區名（如 America/New_York）。默認北京時間；設置後輸入時間按此時區換算為北京時間排盤。農曆輸入時忽略
zhiRunMethodNo置閏方法：chaibu=拆補法（默認），maoshan=茅山法chaibu

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.1.8
    • 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: -"日期（1-31）"New value: +"日 1-31"
    • changedInput schema / properties / hour / description
      Previous value: -"時辰（0-23，24小時制）"New value: +"時 0-23"
    • 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 / minute / description
      Previous value: -"分鐘（0-59）"New value: +"分 0-59，默認 0"
    • changedInput schema / properties / month / description
      Previous value: -"月份（1-12）"New value: +"月 1-12"
    • addedInput schema / properties / timezone
      Added value: +{
+  "description": "IANA 時區名（如 America/New_York）。默認北京時間；設置後輸入時間按此時區換算為北京時間排盤。農曆輸入時忽略",
+  "type": "string"
+}
    • changedInput schema / properties / year / description
      Previous value: -"年份（公曆，1900-2100）"New value: +"公曆年 1900-2100"
  2. First observedv0.1.3

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It thoroughly describes the output contents (e.g., 陰陽遁, 九宮, 八門, 九星, 八神) and the output format (Markdown with ASCII 九宮格), which helps set expectations. It does not explicitly state that the operation is read-only or mention side effects, but for a pure calculation tool this is largely implied and the output disclosure is strong.

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 well-structured with a clear introduction, bullet-pointed output details, and parameter options. It is front-loaded with the core purpose. The background sentence about Qimen being one of the three styles is somewhat extraneous for an agent, and the description is lengthy, but the length is justified by the tool's complexity.

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

Completeness5/5

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

Given the tool's complexity (10 parameters, 3 enums, no output schema) and the absence of annotations, the description is complete enough. It details the output format and contents, explains parameter options, and covers special cases like timezone handling and lunar input. An agent has sufficient information to invoke the tool correctly and understand what it will receive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 10 parameters. However, the description adds meaningful context beyond the schema for several parameters: it explains what each pan type is used for (e.g., 時盤 for immediate prediction) and clarifies the difference between 轉盤 and 飛盤. It does not elaborate on parameters like isLunar or timezone beyond what the schema provides, so it improves semantics without being exhaustive.

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 constructs a basic Qimen Dunjia chart. The parenthetical '基礎' distinguishes it from the sibling tool qimen_yongshen, which likely handles specialized applications. An agent can immediately tell what this tool does and how it differs from related tools.

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 implies usage by stating '輸入時間信息，返回完整的奇門盤面', but it offers no explicit guidance on when to choose this tool over alternatives like qimen_yongshen or other divination tools. The detailed explanations of pan types and styles describe parameter choices rather than tool selection, leaving the when-to-use decision to inference.

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

Deploy Server

Other Tools