Skip to main content
Glama

Qimen Dunjia & BaZi Charts

八字排盘 · BaZi (Four Pillars) Chart

bazi_chart
Read-onlyIdempotent

Cast a BaZi (Four Pillars) natal chart. Deterministic engine (solar-term month pillar, Five-Rats hour rule, true-solar-time ready). Returns pillars with hidden stems and Ten Gods, day master strength evidence chain, geju pattern with grade, favorable/unfavorable elements, current luck cycle. 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": {
      "birthDate": "<birthDate>",
      "birthTime": "<birthTime>"
    },
    "name": "bazi_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoOutput language. Default zh.
genderNoDetermines luck-cycle direction. Default male.
birthDateYesBirth date, YYYY-MM-DD (solar calendar)
birthTimeYesBirth time, HH:MM (24h). Late Zi (23:00-23:59) uses next-day school.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, so the bar is lower; the description still adds real context by asserting the engine is deterministic and spelling out what is produced (hidden stems, Ten Gods, strength evidence chain, geju grade, luck cycle). The quota-free guarantee is a behavioral fact not present in the annotations. It does not cover failure modes for invalid dates, which keeps it below 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.

Conciseness4/5

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

Two front-loaded sentences: purpose first, then engine and outputs. It is dense with domain jargon (geju, Five-Rats) but every clause conveys either capability or a returned artifact. The free-quota note is placed late but is short and earns its spot.

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 return-value burden and does so by enumerating the pillars, Ten Gods, strength chain, pattern grade, and luck cycle. Safety and idempotency are handled by annotations. What remains thin is edge-case behavior for malformed dates or ambiguous birth times, which an agent might want before invoking.

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 baseline is 3. The only parameter remark in the description, "中文/English via lang", restates the lang enum without adding format or fallback detail, and the late-Zi birthTime rule is already documented in the schema.

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?

"Cast a BaZi (Four Pillars) natal chart" states a specific verb and a precisely named resource, then narrows it with engine details (solar-term month pillar, Five-Rats hour rule). The BaZi domain is clearly distinct from the sibling qimen_pan, so an agent can route on name plus first sentence alone.

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 implied rather than stated: the reader infers this is the tool for a birth-chart request and not for a Qi Men divination. The "FREE — no quota consumed" note is a useful selection incentive, but there is no explicit when-to-use, when-not, or named alternative.

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.