AstroWay Chinese metaphysics

Full BaZi chart

astroway_bazi_chart

Read-onlyIdempotent

The four pillars with everything the classical apparatus reads off them in one call: hidden stems, na yin, the twelve stages of the day master, element balance over all eight characters, the strength verdict, symbolic stars from both reference pillars, and the branch and stem interactions. Localised by language. Pass longitude with trueSolarTime true to cut the double-hour from the sun over the birth place; the correction reaches the day and hour only, never the year and month, which turn on world instants.

[Group: BaZi (Four Pillars)] [Endpoint: POST /v1/bazi/chart] [Required: date] [Cost: 20 credits (Tier 2)]

Input Schema

Name	Required	Description
`date`	Yes
`time`	No
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`gender`	No
`language`	No
`timezone`	No	IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
`longitude`	No
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`dayBoundary`	No
`includeLuck`	No
`stageSchool`	No
`trueSolarTime`	No
`timezoneOffset`	No	Ignored when timezone is sent.
`includeFullTable`	No

Output Schema

Name	Required	Description	Default
`notes`	No
`source`	No
`pillars`	No
`language`	No
`strength`	No
`dayMaster`	No
`solarYear`	No
`disclaimer`	No
`methodology`	No
`stageSchool`	No
`interactions`	No
`symbolicStars`	No
`elementBalance`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 13, 2026

addedInput schema / properties / dayBoundary

Added value: +{
+  "enum": [
+    "23:00",
+    "midnight"
+  ],
+  "type": "string"
+}

addedInput schema / properties / gender

Added value: +{
+  "enum": [
+    "male",
+    "female"
+  ],
+  "type": "string"
+}

addedInput schema / properties / includeLuck
```
Added value: +{
+  "type": "boolean"
+}
```

First observedOct 5, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description correctly focuses elsewhere: it discloses that the true-solar-time correction reaches only day and hour, never year or month, and that output is localised by language, plus a cost of 20 credits (Tier 2). These are non-obvious traits not present in the structured fields.

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-loads the payload contents, then gives the one operational caveat; every sentence adds information and the metadata block is compact. The first sentence is an admittedly long enumeration, but it is dense rather than redundant.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the annotations carry the safety profile. Still, for a 14-parameter tool at 29% schema coverage, the description omits the meaning of several behavioural flags and any explicit routing versus the many bazi_* siblings, so an agent cannot call it optimally without more.

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 only 29%, so the description must carry weight, and it does explain the longitude/trueSolarTime interaction and language localisation. However, most parameters (gender, dayBoundary, stageSchool, includeLuck, includeFullTable, time, date) remain undocumented in both schema and description, leaving substantive gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (the full BaZi four-pillar chart) and enumerates exactly what it computes: hidden stems, na yin, twelve stages, element balance, strength verdict, symbolic stars, and stem/branch interactions. The phrase 'in one call' signals it is the aggregate superset, which subtly separates it from the sibling subset tools (bazi_hidden_stems, bazi_na_yin, bazi_strength, etc.), though it never names an alternative outright.

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?

Gives real when-to guidance for one decision – pass longitude with trueSolarTime true to derive the double-hour from the sun – but offers no routing between this aggregate and the individual bazi_* subset tools that return the same components. Usage is implied by 'everything ... in one call' rather than stated.

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

All AstroWay Chinese metaphysics 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?