Skip to main content
Glama

BaZi Annual Pillar

bazi_annual_pillar
Read-onlyIdempotent

Looks up the BaZi annual pillar for any Gregorian year 1–9999, returning its Heavenly Stem, Earthly Branch, animal, element, polarity, and NaYin.

Instructions

Use this when the user asks 'what element is the year of the Snake', 'what's the pillar, stem and branch or NaYin for my birth year' or 'what's the energy of this year' — a single-year lookup beyond the animal. Returns the year's Heavenly Stem, Earthly Branch, animal, element, polarity and NaYin for any year 1-9999.

CREDIT COST: 3 credits per call.

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": {
      "year": "<year>"
    },
    "name": "bazi_annual_pillar"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesGregorian year (1–9999). e.g. 2025.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.8.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds two things annotations cannot: the exact output fields and the cost of 3 credits per call, which materially affects agent budgeting. No pagination or error behavior is mentioned, but for a pure single-value computation that is a minor omission.

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?

Two sentences: the first front-loads the use case and the return payload, the second carries an actionable cost note. Every clause earns its place; nothing is repeated from the schema beyond a single confirmation of the year range.

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

Completeness5/5

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

There is no output schema, and the description compensates by listing every returned field. Combined with the trigger examples, year range, and credit cost, an agent has everything needed to decide and invoke correctly for a one-parameter read-only tool.

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?

With 100% schema coverage the single `year` parameter is already fully documented as 'Gregorian year (1–9999)'. The description restates the 1-9999 range without adding format, calendrical-edge-case, or timezone guidance, so it sits at the baseline for schema-saturated cases.

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 resource (a single year's BaZi pillar) and enumerates exactly what is returned — Heavenly Stem, Earthly Branch, animal, element, polarity, NaYin — over year 1-9999. The phrase 'a single-year lookup beyond the animal' clearly separates it from a full chart tool like explore_bazi_chart, even without naming that sibling.

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 trigger utterances ('what element is the year of the Snake', 'what's the pillar for my birth year') that map cleanly to when to call it, which is stronger than generic guidance. It stops short of explicit exclusions or naming explore_bazi_chart as the alternative for multi-pillar charts, so it is clear context without the when-not-to-call half.

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