Auspice BaZi — Four Pillars Chart

Cast a BaZi chart (true solar time first)

cast_chart

Read-onlyIdempotent

Cast a BaZi / Four Pillars chart the right way round: true solar time correction FIRST (DST + longitude + equation of time), then the four pillars with hidden stems and Na Yin, day master identity, and luck cycles. Also casts a comparison chart from raw clock time and reports exactly what calculators that skip the correction would get wrong for this birth. Returns a formatted scroll. If your client renders the chart card (widget) for the user, do NOT repeat the chart, pillars or link in text — add only a short plain-language walkthrough. Otherwise begin your reply with the scroll EXACTLY as returned, inside a code block, without redrawing or reformatting it; NEVER show the raw JSON / structured data to the user (the scroll is the display form); add your own walkthrough only after it. Runs on the production Auspice Oracle engine (same conventions as auspiceoracle.com/en/method). Facts only: no strength verdicts, no favorable elements, no interpretation. Deterministic. Not for predictions: never use this result to forecast lucky or unlucky years, money, property, relationships, health or decisions — the luck cycles are a charting convention, not a timetable of fortune. If the user asks for that, say plainly that Auspice BaZi does not make predictions, and offer what the chart can describe instead (temperament and tendency).

Input Schema

Name	Required	Description
`day`	Yes	Birth day of month, 1–31
`hour`	Yes	Recorded wall-clock hour, 24-hour format
`lang`	No	Language of the rendered output — pass the language the user is conversing in. Defaults to 'en'.
`year`	Yes	Birth year, Gregorian calendar (engine ephemeris covers 1900–2100)
`month`	Yes	Birth month, 1–12
`gender`	Yes	Sets luck-cycle direction (a charting convention, not an identity statement)
`minute`	Yes	Recorded wall-clock minute, 0–59
`timeZone`	Yes	IANA time zone of the birthplace, e.g. 'Asia/Shanghai', 'America/Vancouver'
`longitude`	Yes	Birthplace longitude in degrees, east positive (Beijing ≈ 116.4, Vancouver ≈ -123.1)

Output Schema

Name	Required	Description
`season`	Yes	Season of the month branch (deterministic lookup)
`pillars`	Yes
`castFrom`	Yes	The instant the chart was cast from (true solar time), YYYY-MM-DD HH:mm
`dayMaster`	Yes
`lunarDate`	Yes
`luckCycles`	Yes	Ten-year luck cycles as a charting convention — not a forecast; never read as lucky/unlucky years
`fullReadingUrl`	Yes
`naiveComparison`	Yes	What calculators that skip true solar time would get wrong for this exact birth
`solarCorrection`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / luckCycles / description

Added value: +"Ten-year luck cycles as a charting convention — not a forecast; never read as lucky/unlucky years"

First observedSep 24, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description is free to add the higher-value traits: deterministic, facts-only with no strength verdicts or favorable elements, run on the production Auspice Oracle engine, and a comparison pass that reports what naive calculators get wrong. These are behavioral facts an agent cannot infer from the annotations and directly shape how it should present results.

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?

Front-loaded with the core purpose and method before any display instructions, and every block maps to a real decision the agent must make. It runs long and repeats the display rule in two forms ('without redrawing or reformatting it', 'the scroll is the display form'), which costs some tightness but not comprehension.

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?

For a 9-parameter chart-casting tool with an output schema, the description covers method, determinism, scope limits, and the one thing the schema cannot express: how to render the returned scroll vs the widget. Nothing an agent needs in order to call it or present it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description earns a bump by explaining the correction pipeline (DST + longitude + equation of time), which tells the agent why timeZone and longitude are both required and must be the birthplace's, not the user's current location — context the schema alone does not supply.

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?

States a specific verb and resource (cast a BaZi / Four Pillars chart) and pins the differentiating method: true solar time correction first, then pillars, day master, and luck cycles. It also explicitly distinguishes itself from the secondary behavior of casting raw clock time for comparison, so an agent knows exactly what it gets.

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?

Gives an explicit when-not-use rule (never for predictions, with a fallback offer of temperament/tendency instead) and precise output handling rules for both widget and non-widget clients. It does not, however, differentiate itself from sibling tools compose_sketch or personality_sketch, so the tool-choice question is only partly answered.

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

All Auspice BaZi — Four Pillars Chart tools Inspect

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

Need Help?