Skip to main content
Glama
Sign In

Qimena Qi Men Dun Jia & BaZi

by io.github.David-rider
OverviewDiscussionsAdmin

Qi Men Dun Jia chart

qimen_chart
Read-onlyIdempotent

Cast an hour-based Qi Men Dun Jia (奇门遁甲) chart for a moment and place: four pillars, ju, Chief Star and Door, and for each of the nine palaces the deity, star, door, heaven/earth/hidden stems, void, horse star, punishment and door pressure, plus detected patterns, palace scores for the chosen focus and the lucky directions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "qimen_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
focusNoWhat the question is about; changes palace scores and lucky directions. Default general.
datetimeNoLocal wall-clock time "YYYY-MM-DDTHH:mm" in `timezone`. Omit for now.
timezoneNoIANA time zone, e.g. "Asia/Shanghai", "America/New_York". Default Asia/Shanghai.
longitudeNoLongitude of the place in degrees, east positive, west negative. Default: the standard meridian of the time zone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description adds significant behavioral context by detailing the complexity and depth of the expected output (e.g., 'deity, star, door, heaven/earth/hidden stems'). This informs the agent that the tool performs deep analysis, going far beyond simple structural execution.

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

Conciseness3/5

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

The tool definition is packed with necessary technical detail, but it is presented as a single, extremely long run-on sentence. While efficient in information density, it lacks structural clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that no output schema exists, the description is exceptionally complete. It outlines every major component that an agent must expect in the response, making it a complete guide for both selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema provides 100% coverage, the description provides critical semantic meaning for the `focus` parameter, clarifying that selecting a focus 'changes palace scores and lucky directions,' thereby explaining the impact of the input on the analysis.

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?

The description is highly specific, stating exactly what is cast (Qi Men Dun Jia chart) and listing all constituent elements of the result, such as 'four pillars,' 'ju,' and 'palace scores.' This leaves no ambiguity for the agent.

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?

While it doesn't offer a formal 'when/when-not' rule, the exhaustive list of output components implies that this tool is intended for the comprehensive, full-fidelity analysis of the chart, distinguishing it from a simpler tool that might only return 'pillars'.

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

All Qimena Qi Men Dun Jia & BaZi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources