Qimen Dunjia & Da Liu Ren divination: complete nine-palace charts and four-lesson analysis.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 2.7/5 across 2 of 2 tools scored.
The two tools target entirely separate divination systems—Da Liu Ren and Qimen Dunjia—with no overlapping concepts or outputs. Each tool has a unique, well-defined purpose, making it unambiguous which to select.
Both tool names follow the identical pattern of [system_name]_calculate, using consistent snake_case. The naming is perfectly predictable and uniform.
With only two tools, the server falls at the lower edge of the typical range. However, since the server is dedicated to exactly two divination systems, one tool per system is a reasonable and focused scope.
Each calculate tool appears to provide a comprehensive output covering core concepts, interpretation guidelines, and common applications for its respective system. There are no obvious missing operations or dead ends for the intended purpose of performing a divination calculation.
da_liu_ren_calculate大六壬排盘C大六壬（Da Liu Ren）是中国古代三式之一，以人事预测见长，擅长判断日常生活中的人事问题。
四课：由日干、日支加上天地盘推演出的四个课位，反映事物的基本结构
三传：初传（发用）、中传、末传，反映事态发展的过程（起始→发展→结局）
十二天将：贵人、腾蛇、朱雀、六合、勾陈、青龙、天空、白虎、太常、玄武、太阴、天后
月将：太阳所在的黄道位置，加于时支之上布天盘
课体：根据四课的推导方式命名（如元首课、重审课、涉害课、遥克课等）
六亲：父母、兄弟、子孙、妻财、官鬼——反映事物之间的生克关系
神煞：驿马、桃花、华盖、天德、月德、旬空等辅助判断
看课体：课体决定了取传方法，不同课体暗示事物的性质
元首课：事情自上而下，领导之象
重审课：需要反复斟酌
涉害课：牵涉面广，事多阻碍
遥克课：远方来事，需等待
看三传：
初传（发用）：事情的起因和开端
中传：事情的发展过程
末传：事情的最终结局
三传递生为吉，递克为凶
看天将：
青龙主吉庆、贵人主贵助
白虎主凶险、玄武主暗昧
看日干旺衰：日干代表求测人，旺则有力，衰则无力
看空亡：旬空之支所临之神/将力量减弱
求财：看妻财爻、青龙、生门
求官：看官鬼爻、朱雀、贵人
婚姻：看天后、六合、妻财爻
疾病：看天医、白虎、病符
出行：看驿马、太冲、天马
| Name | Required | Description | Default |
|---|---|---|---|
| time | No | 时间字符串，格式 YYYY-MM-DD HH:mm:ss。不传则默认使用当前北京时间 | |
| purpose | No | 用途/问题，默认"综合"。如：求财、婚姻、官司、疾病、出行等 | |
| forceDayNight | No | 强制指定昼夜：day（昼贵）或 night（夜贵），影响贵人的顺逆 | |
| trueSolarHour | No | 真太阳时小时数（0-23），用于更精确的时辰判断 |
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.
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.
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.
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.
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.
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.
qimen_dunjia_calculate奇门遁甲排盘C奇门遁甲（Qimen Dunjia）是中国古代三式之一，被称为"帝王之学"。通过天时、地利、人和三维度分析时空能量场。
九宫：坎(1)、坤(2)、震(3)、巽(4)、中(5)、乾(6)、兑(7)、艮(8)、离(9)，对应八方和五行
天盘/地盘：天干在九宫中的分布，天盘为动态，地盘为静态
九星：天蓬、天芮、天冲、天辅、天禽、天心、天柱、天任、天英
八门：休门、生门、伤门、杜门、景门、死门、惊门、开门
八神：值符、腾蛇、太阴、六合、白虎、玄武、九地、九天
值符/值使：当前时刻的主星和主门，是判断吉凶的核心
看值符值使：值符星和值使门的状态决定总体吉凶
看用神宫位：根据用途找到对应宫位（如求财看生门所在宫）
看三奇六仪：乙丙丁为三奇（吉），戊己庚辛壬癸为六仪
看格局：天盘与地盘天干组合形成吉格（如龙遁、虎遁）或凶格（如击刑、入墓）
看空亡：落入空亡的宫位力量减弱
求财：重点看生门、戊
事业：重点看开门、值使
感情：重点看六合、天后
出行：重点看三奇得使、门迫否
| Name | Required | Description | Default |
|---|---|---|---|
| time | No | 时间字符串，格式 YYYY-MM-DD HH:mm:ss。不传则默认使用当前北京时间 | |
| locale | No | 语言代码，默认"zh"（中文）。可选值：zh, en | |
| method | No | 排盘方法，默认"时家"。可选值：时家 | |
| purpose | No | 用途/问题，默认"综合"。如：求财、事业、婚姻、出行、考试、官司等 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, and the description does not contradict this. The description adds background on chart components and interpretation, but it does not disclose tool-specific behaviors such as error handling, timezone handling, or what exactly is returned.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured with clear sections, but it is lengthy and spends many sentences on Qimen education rather than concise tool usage. It is not front-loaded with a direct statement of the tool's operation, making it less efficient than it could be.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, and the description does not explicitly describe the return format or how to interpret the raw output. However, it provides extensive domain context about chart components and interpretation points, which partially compensates for the absence of an output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema covers all 4 parameters with descriptions (100% coverage), so the baseline is 3. The description adds context on purpose values (求财, 事业, etc.) and some domain terms, but it does not clarify parameter formats or defaults beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explains the Qimen Dunjia system extensively but never explicitly states that the tool calculates a chart. The title '奇门遁甲排盘' implies the function, yet the description lacks a direct action statement such as 'Calculates a Qimen Dunjia chart.'
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus the sibling da_liu_ren_calculate. The '常见用途' section lists purposes within Qimen, but it does not help an agent decide between different divination systems.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!