Skip to main content
Glama

Qimen Dunjia & BaZi Charts

奇门遁甲排盘 · Qimen Dunjia Chart

qimen_pan
Read-onlyIdempotent

Cast a Qimen Dunjia (奇门遁甲) chart for a given date/time. Deterministic engine (Zhi Run method, verified against classical case ledger). Returns the 9-palace chart, deities/stars/gates, void palaces, detected formations (geju) and a rule-based reading. FREE — no quota consumed. 中文/English via lang.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>",
      "time": "<time>"
    },
    "name": "qimen_pan"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesSolar date, YYYY-MM-DD
langNoOutput language. Default zh.
timeYes24h time, HH:MM
sceneNoQuestion scene. Default general.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, open-world), the description adds genuinely new behavioral facts: the engine is deterministic, validated against a classical case ledger, and free of quota cost. It also enumerates the return contents, which matters because no output schema exists. It does not cover latency or input validation behavior, so not a 5.

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

Conciseness5/5

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

Two tight sentences: the first front-loads what the tool does, the second packs engine provenance, return contents, cost, and language support without a wasted clause. Dense but readable.

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 carries the burden of describing returns, and it does so by naming the 9-palace chart, deities/stars/gates, void palaces, formations, and rule-based reading. It leaves the role of the `scene` parameter unexplained, which is the main remaining gap for a four-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 four parameters are already documented in the schema, and the description only restates the `lang` option (中文/English). It adds no meaning about how `scene` influences the reading or what format `date`/`time` must take beyond the schema, so the baseline of 3 applies.

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?

The description opens with a specific verb and resource: "Cast a Qimen Dunjia (奇门遁甲) chart for a given date/time," which is precise and unambiguous. It does not explicitly contrast with the sibling bazi_chart, relying on the distinct system name to differentiate, so it stops short of a 5.

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?

Usage is only implied by the input shape — the presence of a `scene` parameter hints at question-based casting, but the description never states when to choose this tool over bazi_chart or when not to use it. No prerequisites or exclusions are given.

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.