Skip to main content
Glama

Get Chinese Astrology

BaZi chart

get_bazi_chart
Read-onlyIdempotent

Calculates the Four Pillars (BaZi) chart for a birth date, an optional birth time and the birthplace time zone. Returns the year, month, day and hour pillars, the Day Master, each stem's Ten Gods relation to it, the hidden stems in each branch and the five-element count.

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": {
      "birthDate": "<birthDate>"
    },
    "name": "get_bazi_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNoLocal birth time as HH:MM on a 24-hour clock. Without it the chart has no hour pillar and is read at midday.
timeZoneNoIANA time zone of the birthplace, such as Asia/Shanghai, Asia/Tokyo or America/New_York. Asia/Shanghai when absent.
birthDateYesBirth date as YYYY-MM-DD, from 1901-02-19 to 2100-02-08.

Output Schema

NameRequiredDescriptionDefault
itemYes
viewYes
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description's help. The description adds modest value by enumerating what the computation produces (pillars, Day Master, Ten Gods, hidden stems, element counts), though this largely restates the output schema. It does not say whether results are deterministic across calls or how missing inputs are defaulted, beyond calling them optional.

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?

A single front-loaded sentence that names the operation before listing inputs and outputs, with no filler or hedging. The trailing enumeration of returned components is somewhat long and partly duplicates the output schema, which keeps it just below the top mark.

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?

For a three-parameter, read-only calculation tool with a fully documented schema, annotations, and an output schema, the description covers purpose, required inputs, and returned content adequately. The only meaningful gap is the absence of any guidance on when this chart is preferable to the sibling chart tools.

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%, with the date format and range, the HH:MM pattern and the IANA time zone and its default all documented in the schema itself. The description only echoes those three inputs at a high level and adds no format, default, or validation detail beyond them, so the baseline of 3 applies.

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?

The description opens with a specific verb and resource ("Calculates the Four Pillars (BaZi) chart") and states the inputs it consumes and the outputs it produces. The resource is distinct enough from siblings like get_zi_wei_chart that an agent can distinguish it, but the description never names or contrasts those alternatives explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no mention of alternatives such as get_zi_wei_chart for a different chart system, and no statement of prerequisites. The mention of "an optional birth time" implies a use case but does not route the agent between tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.