Skip to main content
Glama

explore_bazi_chart

Read-onlyIdempotent

Generate an interactive BaZi chart with clickable pillars. Each pillar reveals stem, branch, Ten God, element color, Day Master, and Wu Xing balance. Click pillars for life-domain interpretations.

Instructions

Generate an interactive BaZi (四柱命盘 Four Pillars of Destiny) chart with clickable pillars.

Returns an embedded visual Four Pillars explorer showing the Year, Month, Day, and Hour pillars — each with its Heavenly Stem (天干) and Earthly Branch (地支), Ten God label, and element color — plus the Day Master identity and a Wu Xing (五行) element balance bar. Click any pillar for an instant interpretation of what it reveals about that life domain (Year = ancestry/early life, Month = parents/career, Day = self/spouse, Hour = children/later life).

CREDIT COST: 3 credits per call (1 base + 2 visual render).

Use this for a rich, interactive BaZi experience in MCP Apps-capable hosts (Claude Desktop). Falls back to a text summary in other hosts, so it is also the right call without a renderer. Deeper derivations (Ten Gods, element balance, luck pillars) and a plain non-visual pillars lookup have dedicated tools on the full surface (?profile=full).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayNoBirth day of month (1–31).
hourNoBirth hour (0–23). Optional, defaults to 12 (noon). Chinese shí hours are 2-hour blocks — precision within a 2-hour window is sufficient.
yearNoGregorian birth year, e.g. 1987.
monthNoBirth month (1–12).
datetimeNoAlternative to year/month/day: ISO 8601 datetime read as LOCAL wall-clock time at the birth place — BaZi pillars are local by definition, so a zone-less value is correct here and is NOT converted to UTC. If it carries a 'Z' or offset, also pass timezone.
timezoneNoIANA timezone name for the birth place, e.g. 'Asia/Shanghai'. Only needed when datetime carries a 'Z' or ±HH:MM offset.
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description discloses a credit cost ('CREDIT COST: 3 credits per call'), interactive behavior ('Click any pillar for an instant interpretation'), and host-dependent fallback behavior. This substantially enriches the agent's understanding of side effects and requirements without contradicting annotations.

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?

The description is well-structured and information-dense: it states the core function, enumerates return contents, explains interactivity, discloses cost, and gives usage guidance—all in a compact, logically ordered format without redundancy or fluff.

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 the tool's complexity and the absence of an output schema, the description fully specifies the return value (pillars, Heavenly Stem, Earthly Branch, Ten God, element color, Day Master, Wu Xing balance bar), interaction model, cost, fallback behavior, and differentiation from sibling tools. No critical information is missing.

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% and the schema itself provides detailed parameter descriptions (e.g., hour precision in 2-hour blocks, timezone guidance). The main description adds no parameter-specific detail beyond what the schema already documents, so the baseline of 3 is appropriate.

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 opens with a specific verb+resource: 'Generate an interactive BaZi (四柱命盘 Four Pillars of Destiny) chart with clickable pillars.' It clearly distinguishes this tool from siblings by explicitly naming dedicated tools for deeper derivations and plain non-visual lookup, making its scope unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance: 'Use this for a rich, interactive BaZi experience in MCP Apps-capable hosts (Claude Desktop).' It also covers fallback usage ('Falls back to a text summary in other hosts, so it is also the right call without a renderer') and names alternatives for deeper derivations and plain lookup, which is exemplary.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/openephemeris/openephemeris-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server