Skip to main content
Glama

衍象坊 · 奇门遁甲 & 大六壬

大六壬排盘

da_liu_ren_calculate
Read-only

大六壬(Da Liu Ren)是中国古代三式之一,以人事预测见长,擅长判断日常生活中的人事问题。

核心概念

  • 四课:由日干、日支加上天地盘推演出的四个课位,反映事物的基本结构

  • 三传:初传(发用)、中传、末传,反映事态发展的过程(起始→发展→结局)

  • 十二天将:贵人、腾蛇、朱雀、六合、勾陈、青龙、天空、白虎、太常、玄武、太阴、天后

  • 月将:太阳所在的黄道位置,加于时支之上布天盘

  • 课体:根据四课的推导方式命名(如元首课、重审课、涉害课、遥克课等)

  • 六亲:父母、兄弟、子孙、妻财、官鬼——反映事物之间的生克关系

  • 神煞:驿马、桃花、华盖、天德、月德、旬空等辅助判断

解读要点

  1. 看课体:课体决定了取传方法,不同课体暗示事物的性质

    • 元首课:事情自上而下,领导之象

    • 重审课:需要反复斟酌

    • 涉害课:牵涉面广,事多阻碍

    • 遥克课:远方来事,需等待

  2. 看三传

    • 初传(发用):事情的起因和开端

    • 中传:事情的发展过程

    • 末传:事情的最终结局

    • 三传递生为吉,递克为凶

  3. 看天将

    • 青龙主吉庆、贵人主贵助

    • 白虎主凶险、玄武主暗昧

  4. 看日干旺衰:日干代表求测人,旺则有力,衰则无力

  5. 看空亡:旬空之支所临之神/将力量减弱

常见用途

  • 求财:看妻财爻、青龙、生门

  • 求官:看官鬼爻、朱雀、贵人

  • 婚姻:看天后、六合、妻财爻

  • 疾病:看天医、白虎、病符

  • 出行:看驿马、太冲、天马

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeNo时间字符串,格式 YYYY-MM-DD HH:mm:ss。不传则默认使用当前北京时间
purposeNo用途/问题,默认"综合"。如:求财、婚姻、官司、疾病、出行等
forceDayNightNo强制指定昼夜:day(昼贵)或 night(夜贵),影响贵人的顺逆
trueSolarHourNo真太阳时小时数(0-23),用于更精确的时辰判断

TDQS

C2.5/5.0
Behavior2/5

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

Annotations state readOnlyHint=true, and the description does not contradict this. However, beyond that, the description offers no behavioral disclosure: it doesn't explain what the output looks like, whether results are deterministic, default time handling, or any side effects. The extensive domain knowledge about 四课 and 三传 is useful context but doesn't describe the tool's runtime behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a comprehensive essay on Da Liu Ren theory, including core concepts, interpretation points, and common uses. It is well-structured with headings and bullets, but it is far longer than needed for tool selection and invocation. The opening is about the tradition, not the tool's purpose, so it is not front-loaded with actionable information.

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?

The description thoroughly covers the domain, which helps the agent interpret the chart's concepts (天将, 六亲, 神煞, etc.). However, it never states what the tool actually returns—there is no output schema, and the description doesn't describe the result format, so this is a gap. Nonetheless, the rich domain context partially compensates for the complexity of the subject.

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?

The input schema has 100% coverage with descriptions for all four parameters (time, purpose, forceDayNight, trueSolarHour). The description adds zero parameter-specific guidance, so it adds no value beyond the schema. Baseline 3 applies since the schema fully explains each parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The title clearly indicates Da Liu Ren calculation, but the description itself never explicitly states what the tool does. It opens with the tradition ('大六壬是中国古代三式之一') and provides background, but there is no direct sentence like 'Calculates a Da Liu Ren chart for the given time.' The purpose is implied rather than stated.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives (e.g., the sibling qimen_dunjia_calculate). The '常见用途' section lists divination topics (求财, 婚姻, etc.) but these are interpretative themes, not selection criteria. No exclusions, prerequisites, or alternative tool mentions are provided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.9/5.0
Disambiguation5/5

The two tools, da_liu_ren_calculate and qimen_dunjia_calculate, target completely distinct traditional Chinese metaphysical systems. Their descriptions clearly differentiate their unique frameworks (e.g., '四课三传' for Da Liu Ren and '九宫八门' for Qimen Dunjia), leaving no ambiguity about which to use for a given prediction need.

Naming Consistency4/5

Both tool names follow a consistent pattern of pinyin_verb_noun, specifically using Chinese phonetic transliteration. While the naming is clear and descriptive for those familiar with these systems, the inclusion of special characters (·) and non-standard capitalization (first letter lowercase, rest following dots or spaces) could be seen as a minor deviation from a strict snake_case or camelCase system, but remains highly readable.

Tool Count2/5

With only two tools for a server named '衍象坊 · 奇门遁甲 & 大六壬', the tool count is surprisingly low. Each system is incredibly deep and complex, typically requiring numerous specialized operations for different divination methods. Two tools suggest a shallow integration that may not cover the full scope of either system, feeling too sparse for comprehensive use.

Completeness1/5

The tool set is severely incomplete for both the Da Liu Ren and Qimen Dunjia systems. Each system includes multiple subsets like 'Zhi Fa', 'Luo Shu', or 'Zhuan Ming', which are not covered. The one-calculate-tool-per-system approach leaves no room for specifying input parameters (e.g., date, time, location) or handling different question types, making it impossible to use these tools for actual divination in a real-world scenario.

Resources