Skip to main content
Glama
Four Pillars MCP Server

Four Pillars MCP Server

calculate_four_pillars

Read-onlyIdempotent

Calculate a BaZi chart from birth date, local time, IANA timezone, and longitude using true solar time and solar-term boundaries; returns reproducible pillars and provenance.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "<date>",
      "time": "<time>",
      "timezone": "<timezone>",
      "longitude": "<longitude>"
    },
    "name": "calculate_four_pillars"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesLocal civil date in YYYY-MM-DD format.
timeYesLocal civil time in HH:mm format.
latitudeNoOptional birth latitude in decimal degrees.
timezoneYesIANA time zone, for example Asia/Shanghai or America/Los_Angeles.
longitudeYesBirth longitude in decimal degrees, east positive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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, closed-world, non-destructive), so the description's added value is the computational model: local apparent true solar time, astronomical solar-term boundaries, and the 23:00 Zi-hour next-day rollover. Those conventions materially affect results and are not derivable from structured fields, though it says nothing about failure behavior for invalid timezones or dates.

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?

Three sentences, each load-bearing: inputs first, then the calculation conventions that determine correctness, then the output scope. No filler or restatement of the name.

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

Completeness4/5

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

With no output schema, the description correctly carries the return-value burden by stating it returns reproducible chart facts plus provenance and nothing interpretive. The only notable omissions are how the optional latitude is used (or ignored) and what happens on invalid inputs.

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 schema already documents formats and ranges for all five parameters. The description only adds the implicit relationship that longitude and timezone feed the true-solar-time correction, and it omits the optional latitude parameter entirely, so it stays at the baseline for schema-heavy tools.

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 resource ("Calculate the BaZi (Four Pillars) chart") and immediately scopes what the tool is not ("not interpretation or prediction"), so an agent can tell a chart-computation tool apart from an interpretive one without inspecting the schema.

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?

It gives a clear usage context — computing a chart from birth data under specific astronomical conventions — and explicitly excludes interpretive/predictive use. There is no sibling catalog to route against, so the absence of named alternatives is not a real gap, but no explicit preconditions (e.g. valid IANA zone, data quality requirements) are stated.

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

Deploy Server

Other Tools