Skip to main content
Glama

Totally Tarot Calculators

Four pillars (BaZi) of a birth

compute_four_pillars
Read-onlyIdempotent

Computes the four pillars (BaZi) of a birth: the stem and branch of the year, month, day and hour, and each pair's place in the sixty cycle. Stems and branches only, no interpretation. Takes "date", "time" and "place".

The month changes at the solar terms, and the hour needs the birthplace's historic UTC offset. Without a birth time the call returns a time_required refusal.

Results include an attribution line and a permalink.

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>",
      "place": "<place>"
    },
    "name": "compute_four_pillars"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, ISO YYYY-MM-DD, Dec 1926-2100. Example: "1990-06-15".
timeYesBirth time HH:MM, local at the birthplace. Example: "08:30". Required.
placeYesTown or city of birth with region or country. Example: "Chicago, Illinois, US".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and non-open-world, so the bar is lower, yet the description still adds real behavior: the solar-term month boundary, the dependency on historic UTC offsets for the hour pillar, an explicit refusal mode (time_required), and the fact that results carry an attribution line and permalink. None of this is recoverable from the annotations or schema.

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?

Three short paragraphs, front-loaded with the computation and its output components, then constraints, then result characteristics. The only waste is the 'Takes date, time and place' clause, which duplicates information the schema already carries.

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 must sketch the return, and it does name the computed components plus attribution and permalink. It leaves a few things implicit, such as how the pillars are structured in the response and whether the range limit is enforced as an error, but nothing critical to correct invocation 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 the schema already documents date, time and place; the sentence 'Takes date, time and place' merely restates it. However, the note that the hour needs the birthplace's historic UTC offset adds genuine semantic weight to 'place' and 'time' beyond their schema descriptions.

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 (computes the four pillars/BaZi of a birth) and enumerates the exact outputs: year, month, day and hour stem/branch plus each pair's position in the sixty cycle. The clause 'Stems and branches only, no interpretation' draws a clear boundary that separates it from interpretation-oriented siblings like compute_birth_chart.

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 concrete prerequisites and error behavior: all three inputs are required, the month is keyed to solar terms, the hour requires the birthplace's historic UTC offset, and a missing birth time yields a time_required refusal. It stops short of naming an alternative tool for the no-birth-time case, so the agent must infer that path itself.

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.

Resources