Skip to main content
Glama
ChesterRa

命盘 Mingpan

by ChesterRa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

梅花易數排盤

meihua_basic

Generate a Plum Blossom divination chart from a timestamp or two numbers, returning hexagrams, trigrams, moving line, and body-use elemental analysis in Markdown for AI interpretation.

Instructions

梅花易數排盤（基礎排盤）。

支持兩種起卦方式：

  1. 時間起卦（method='time'）：根據農曆年月日時起卦

  2. 數字起卦（method='number'）：根據兩個數字起卦

返回完整的梅花盤面：

  • 本卦/變卦/互卦

  • 上卦/下卦（含卦象、五行）

  • 動爻位置

  • 體用分析（體卦、用卦、五行生剋關係）

  • 起卦數據詳情

時間起卦算法（農曆）：

  • 上卦 = (年支序數 + 月 + 日) % 8

  • 下卦 = (年支序數 + 月 + 日 + 時辰序數) % 8

  • 動爻 = (年支序數 + 月 + 日 + 時辰序數) % 6

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayNo起卦日期（1-31，time 模式必填）
hourNo起卦時辰（0-23，time 模式必填）
yearNo起卦年份（公曆，time 模式必填）
monthNo起卦月份（1-12，time 模式必填）
methodYes起卦方式：time=時間起卦，number=數字起卦
isLunarNo輸入是否為農曆，默認 false
timezoneNoIANA 時區名（time 模式，默認北京時間）
yaoNumberNo動爻數（可選，默認用上下卦數之和）
lowerNumberNo下卦數（number 模式必填）
upperNumberNo上卦數（number 模式必填）

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 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 / isLunar / description
      Previous value: -"Whether the input date is in lunar calendar (農曆). If true, will be converted to solar calendar internally."New value: +"輸入是否為農曆，默認 false"
    • addedInput schema / properties / lowerNumber / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / timezone
      Added value: +{
+  "description": "IANA 時區名（time 模式，默認北京時間）",
+  "type": "string"
+}
    • addedInput schema / properties / upperNumber / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / yaoNumber / maximum
      Added value: +9007199254740991
  2. First observedv0.1.3

TDQS

A3.7/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 complete return contents (本卦/變卦/互卦, 體用分析, 動爻) and the output format (Markdown). It omits error/validation behavior and timezone-default nuances, keeping it below 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?

Front-loaded summary followed by tightly bulleted modes and return fields; the embedded 農曆 algorithm formulas are arguably load-bearing since they explain the resulting 卦. Slightly long, but every section contributes.

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 10-parameter tool with no annotations and no output schema, the description compensates by enumerating return values, mode selection and output format. Remaining gaps are minor edge-case behaviors rather than core task information.

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 baseline is 3. The description reinforces the method enum and the lunar/time-based casting logic, but adds little syntax beyond what the schema already documents for each parameter.

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?

States a specific verb+resource (梅花易數排盤/起卦) and enumerates its two casting modes and full output structure. An agent can tell what the tool does without opening the schema, though it never names how it differs from sibling systems like qimen_basic or liuyao_basic.

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?

It explains the conditions for the two modes (time vs number), which is implied guidance for choosing method. However, there is no explicit when-to-use/when-not or routing versus the many sibling divination tools, so usage is only partially addressed.

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