Skip to main content
Glama

explore_bazi_chart

Read-onlyIdempotent

Generate an interactive Four Pillars (BaZi) chart. Click any pillar for life-domain interpretations (ancestry, parents/career, self/spouse, children) and view the Wu Xing element balance bar.

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).
minuteNoBirth minute (0–59). Optional, defaults to 0. Only matters under true_solar_time or near a boundary.
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.
latitudeNoBirth latitude, decimal degrees (north+).
timezoneNoIANA timezone name for the birth place, e.g. 'Asia/Shanghai'. Required to convert a zoned datetime back to local clock; also frames the year/month solar-term boundary.
longitudeNoBirth longitude, decimal degrees (east+).
day_boundaryNoDay-pillar cutover convention. Default zi_hour.
year_boundaryNoYear-pillar cutover convention. Default lichun.
true_solar_timeNoApply true solar time correction (needs latitude+longitude).
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the bar is lower, but the description adds substantial behavioral context: a credit cost of 3 credits per call, an interactive visual output with fallback to text in non-MCP hosts, and clickable pillar behavior with life-domain interpretations. No contradiction with annotations; instead, it enriches the safety profile with cost and rendering behavior.

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 front-loaded with the core action, then returns, then credit cost, then usage routing. Each sentence earns its place: the output details are concrete, the credit cost is a clearly scannable block, and the fallback/host guidance is actionable. There is no redundancy or filler despite the length.

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?

With 12 parameters (0 required) and no output schema, the description compensates by thoroughly describing the output payload: four pillars, Heavenly Stems, Earthly Branches, Ten Gods, element colors, Day Master, Wu Xing balance bar, and click interpretations. It also addresses host-based rendering differences and credit pricing. The schema already covers edge-case parameter details, so nothing needed for correct invocation 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%, so the baseline is 3 and the schema already documents all 12 parameters in detail. The tool description does not add parameter-level meaning beyond what the schema provides; it only references the hour default, which is already in the schema. The schema parameters carry the semantic weight here.

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 and deliverable: 'Generate an interactive BaZi (四柱命盘 Four Pillars of Destiny) chart with clickable pillars.' It distinguishes this tool from siblings by emphasizing the interactive, visual nature and explicitly noting that deeper derivations and a plain non-visual lookup have separate tools. The purpose is unambiguous and clearly scoped.

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)' and states that it falls back to a text summary in other hosts, making it 'also the right call without a renderer.' It also names what it is not for by directing users to dedicated tools for deeper derivations and non-visual lookup on `?profile=full`. This is model-level routing clarity.

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

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