Four Pillars MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server calculates deterministic BaZi Four Pillars from explicit date, time, IANA timezone, and longitude. It does not geocode addresses, store personal data, generate interpretations, or calculate luck cycles.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calculate_four_pillarsA | Calculate the BaZi (Four Pillars) chart from a local birth date, time, IANA timezone, and decimal longitude. The calculation uses local apparent true solar time, astronomical solar-term boundaries, and the 23:00 Zi-hour next-day boundary. Returns only reproducible chart facts and provenance, not interpretation or prediction. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool in the set, there is no possibility of misselection or overlap. The tool's purpose (compute a BaZi chart from birth data) is unambiguous and clearly stated.
The single name calculate_four_pillars follows a clean verb_noun snake_case convention. There is no competing convention to create inconsistency.
One tool is on the thin side even for a narrowly scoped domain. The server is defensible as a single-purpose calculator, but a single operation gives an agent no alternative entry points.
The core calculation is covered, but the surface stops there. Useful companions such as solar-term lookup, current-pillar calculation, or input validation (timezone/longitude checks) are absent, leaving dead ends for follow-up questions.