Skip to main content
Glama
ChesterRa

命盘 Mingpan

by ChesterRa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

六爻排盤

liuyao_basic

Generate a complete Six Lines divination chart from six yao values and a date/time, including hexagrams, six relatives, six gods, moving lines, and calendar details for analysis.

Instructions

六爻排盤（基礎排盤）。

輸入六個爻值和起卦時間，返回完整的六爻盤面：

  • 本卦/變卦（含卦名、卦宮、五行）

  • 六爻納甲（每爻地支及五行）

  • 六親（父母/兄弟/子孫/妻財/官鬼）

  • 六神（青龍/朱雀/勾陳/螣蛇/白虎/玄武）

  • 世應位置

  • 動爻標註

  • 日干支、月建、旬空

爻值說明：

  • 6 = 老陰（動爻，陰變陽）

  • 7 = 少陽（靜爻，陽）

  • 8 = 少陰（靜爻，陰）

  • 9 = 老陽（動爻，陽變陰）

輸入順序：自下而上（初爻到上爻） 起卦時間默認北京時間，可提供 timezone 换算。

輸出為 Markdown 格式，便於 AI 分析解讀。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayYes日 1-31
hourYes時 0-23
yearYes公曆年 1900-2100
monthYes月 1-12
minuteNo分 0-59，默認 0
isLunarNo輸入日期是否為農曆，默認公曆
timezoneNoIANA 時區名（如 America/New_York）。默認北京時間；設置後輸入時間按此時區換算為北京時間排盤。農曆輸入時忽略
yaoValuesYes六個爻值（自下而上，初爻到上爻）。6=老陰(動), 7=少陽(靜), 8=少陰(靜), 9=老陽(動)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 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）"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: +"輸入日期是否為農曆，默認公曆"
    • addedInput schema / properties / minute
      Added value: +{
+  "default": 0,
+  "description": "分 0-59，默認 0",
+  "maximum": 59,
+  "minimum": 0,
+  "type": "integer"
+}
    • 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 / yaoValues / items
      Previous value: -[
-  {
-    "enum": [
-      6,
-      7,
-      8,
-      9
-    ],
-    "type": "number"
-  },
-  {
-    "enum": [
-      6,
-      7,
-      8,
-      9
-    ],
-    "type": "number"
-  },
-  {
-    "enum": [
-      6,
-      7,
-      8,
-      9
-    ],
-    "type": "number"
-  },
-  {
-    "enum": [
-      6,
-      7,
-      8,
-      9
-    ],
-    "type": "number"
-  },
-  {
-    "enum": [
-      6,
-      7,
-      8,
-      9
-    ],
-    "type": "number"
-  },
-  {
-    "enum": [
-      6,
-      7,
-      8,
-      9
-    ],
-    "type": "number"
-  }
-]New value: +false
    • addedInput schema / properties / yaoValues / prefixItems
      Added value: +[
+  {
+    "anyOf": [
+      {
+        "const": 6,
+        "type": "number"
+      },
+      {
+        "const": 7,
+        "type": "number"
+      },
+      {
+        "const": 8,
+        "type": "number"
+      },
+      {
+        "const": 9,
+        "type": "number"
+      }
+    ]
+  },
+  {
+    "anyOf": [
+      {
+        "const": 6,
+        "type": "number"
+      },
+      {
+        "const": 7,
+        "type": "number"
+      },
+      {
+        "const": 8,
+        "type": "number"
+      },
+      {
+        "const": 9,
+        "type": "number"
+      }
+    ]
+  },
+  {
+    "anyOf": [
+      {
+        "const": 6,
+        "type": "number"
+      },
+      {
+        "const": 7,
+        "type": "number"
+      },
+      {
+        "const": 8,
+        "type": "number"
+      },
+      {
+        "const": 9,
+        "type": "number"
+      }
+    ]
+  },
+  {
+    "anyOf": [
+      {
+        "const": 6,
+        "type": "number"
+      },
+      {
+        "const": 7,
+        "type": "number"
+      },
+      {
+        "const": 8,
+        "type": "number"
+      },
+      {
+        "const": 9,
+        "type": "number"
+      }
+    ]
+  },
+  {
+    "anyOf": [
+      {
+        "const": 6,
+        "type": "number"
+      },
+      {
+        "const": 7,
+        "type": "number"
+      },
+      {
+        "const": 8,
+        "type": "number"
+      },
+      {
+        "const": 9,
+        "type": "number"
+      }
+    ]
+  },
+  {
+    "anyOf": [
+      {
+        "const": 6,
+        "type": "number"
+      },
+      {
+        "const": 7,
+        "type": "number"
+      },
+      {
+        "const": 8,
+        "type": "number"
+      },
+      {
+        "const": 9,
+        "type": "number"
+      }
+    ]
+  }
+]
    • changedInput schema / properties / year / description
      Previous value: -"起卦年份（公曆）"New value: +"公曆年 1900-2100"
  2. First observedv0.1.3

TDQS

A3.9/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 and does so well: it discloses the default Beijing time, timezone conversion behavior, lunar/gregorian handling, and that output is Markdown. It omits any permission/rate/error behavior, but for a pure computation tool the defaults and output format are the material traits.

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?

Front-loads the purpose, then uses structured bullets for the return contents and a clear '爻值說明' block for the input encoding. Efficient overall, though the long enumerated return list is more than strictly needed for argument selection.

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?

With no output schema, the description usefully enumerates the returned chart components (本卦/變卦, 納甲, 六親, 六神, 世應, 動爻, 日干支/月建/旬空) and covers time defaults, making it sufficient for correct invocation of a complex 8-parameter tool.

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 all 8 parameters are already documented, including the yaoValues enumeration and timezone/lunar semantics. The description restates the 6/7/8/9 meanings and input order rather than adding new meaning, so baseline 3 applies.

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?

States a specific verb+resource (六爻排盤 基礎排盤) and the divination method itself cleanly distinguishes it from the sibling divination tools (meihua_basic, daliuren_basic, qimen_basic, bazi_basic). An agent can tell exactly which system produces the chart 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?

The description explains the mechanics of the input (yao value meanings, bottom-to-top order, time defaults) but offers no guidance on when to choose this tool over the other divination siblings. Usage is implied by the method name only, not stated.

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