命盘 Mingpan

奇門用神分析

qimen_yongshen

Selects and analyzes the correct Yong Shen for Qimen Dunjia divination based on 14 matter types, outputting deterministic facts like palace location, state, and relationships for AI interpretation.

Instructions

奇門遁甲用神分析。

在基礎排盤基礎上，根據事類選取用神並分析：

支持 14 種事類：求財、婚姻、疾病、出行、訴訟、考試、工作、失物、置業、求官、孕產、尋人、合作、其他

分析內容（僅確定性事實）：

主用神/輔用神識別及落宮（依《神奇之門》通行用神表）
用神旺相休囚死狀態（依月令）
用神空亡、入墓、擊刑檢測
與日干生克關係
主客落宮與生克關係（涉及雙方的事類）
年命落宮（可選）

定位說明：用神吉凶、格局利弊等判斷無權威統一口徑，請由 AI 結合盤面（含格局檢測）自行分析。

輸出為結構化 Markdown，便於 AI 斷卦分析。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`day`	Yes	日 1-31
`hour`	Yes	時 0-23
`year`	Yes	公曆年 1900-2100
`month`	Yes	月 1-12
`minute`	No	分 0-59，默認 0
`shiLei`	Yes	事類（用於確定用神）
`isLunar`	No	輸入日期是否為農曆，默認公曆
`nianGan`	No	年干（用於年命分析，可選）
`panType`	No	盤類型：时盘（默認）、日盘、月盘、年盘	时盘
`panStyle`	No	盤式：转盘（默認，遵循《神奇之門》）或飞盘	转盘
`timezone`	No	IANA 時區名（如 America/New_York）。默認北京時間；設置後輸入時間按此時區換算為北京時間排盤。農曆輸入時忽略
`zhiRunMethod`	No	置閏方法：chaibu=拆補法（默認），maoshan=茅山法	chaibu
`includeShenSha`	No	是否包含神煞分析

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.1.8Sep 30, 2026

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"

changedInput schema / properties / panStyle / description

Previous value: -"盤式：转盘（默認）或飞盘"New value: +"盤式：转盘（默認，遵循《神奇之門》）或飞盘"

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"

changedInput schema / properties / zhiRunMethod / description

Previous value: -"置閏方法"New value: +"置閏方法：chaibu=拆補法（默認），maoshan=茅山法"

First observedv0.1.3Jun 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully delimits scope by declaring analysis is "僅確定性事實" and explicitly declining to judge auspiciousness (leaving that to the AI), and it states the output is structured Markdown — meaningful behavioral disclosure for a pure-computation tool.

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 with the one-line purpose, then organized under bolded sub-headers and a bulleted analysis list. Appropriately sized for a complex 13-parameter tool, though a few lines are near-redundant with the schema enums.

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?

No output schema exists, but the description enumerates the analysis components and describes the return format (structured Markdown), which is what an agent needs here. Given the tool's complexity, this is close to complete, with only the prerequisite on qimen_basic left implicit.

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 schema already documents all 13 parameters including the 14-value shiLei enum. The description restates the matter categories and mentions nianGan-driven 年命落宮, but adds no syntax or format detail beyond what the schema provides; 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: selects the yongshen (用神) by matter category and analyzes it. It also anchors itself as extending qimen_basic ("在基礎排盤基礎上"), so an agent can distinguish it from the sibling 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 Guidelines4/5

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

Implies the usage context clearly: run it after a basic chart, driven by a matter category (14 enumerated). It establishes its relationship to qimen_basic but never names an explicit alternative or states when NOT to use it, so it stops short of a full when/when-not routing.

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

Deploy Server

奇門用神分析

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools