Skip to main content
Glama

Calcgrid

by com.tttkmbb
OverviewDiscussionsAdmin

Chinese Zodiac Calculator (生肖)

find_chinese_zodiac
Read-onlyIdempotent

Use this when you need someone's Chinese zodiac sign and element from a Gregorian birth date, especially for January–February births where the boundary matters, or the sign's traditional compatibility groups. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery.

Do not use this when you need a full Bazi chart with month, day and hour pillars (use bazi-four-pillars), or the Western star sign (use zodiac). What it computes: Finds the Chinese zodiac animal (生肖 shengxiao), sexagenary year (干支 ganzhi), stem element, yin/yang, nayin (纳音) and fixed element for a birth date, using either the Chinese New Year boundary or the 立春 (Lichun) boundary, plus the traditional relationship groups (六合, 三合, 六冲, 六害, 相刑) and 本命年 years. Inputs: birth_date (date); boundary (enum, optional); reference_year (integer, optional). Complete JSON argument examples: {"birth_date":"1990-02-10","boundary":"lunar_new_year","reference_year":2026} | {"birth_date":"1990-02-03","boundary":"lichun"} Outputs: zodiac, zodiac_cn, year_ganzhi, year_ganzhi_pinyin, year_english, stem_element, yin_yang, nayin, animal_fixed_element, year_used, chinese_new_year_date, lichun_datetime, boundary_note, benmingnian_years, secret_friend, trine_partners, clash, harm, punishment, age_in_reference_year [years], is_benmingnian_in_reference_year, reference_year_zodiac. Formula: year_used = Gregorian year, minus 1 when birth_date is before Chinese New Year (or before 立春 with boundary = lichun); ganzhi index = (year_used − 4) mod 60; animal = branch = index mod 12; 六合 partner = (13 − b) mod 12; 三合 = b ± 4; 六冲 = b + 6; 六害 partner = (7 − b) mod 12 Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/chinese-zodiac with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/lunar/chinese-zodiac.md

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boundaryNoWhich event starts the zodiac year: Chinese New Year (popular usage, default) or 立春 around 4 February (astrological usage).lunar_new_year
birth_dateYesGregorian birth date (civil date in China Standard Time), 1900–2100.
reference_yearNoOptional Gregorian year for which to report the age and whether it is a 本命年.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
linksNo
resultYes
requestYes
sourcesNo
successYes
versionNo
freshnessNo
timestampYes
next_actionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "birth_date": "1990-02-10",
+    "boundary": "lunar_new_year",
+    "reference_year": 2026
+  },
+  {
+    "birth_date": "1990-02-03",
+    "boundary": "lichun"
+  }
+]
  2. Added
  3. Removed
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark it read-only, idempotent, and non-destructive. The description adds rich behavioral context: boundary selection rules, the exact year and ganzhi formula, the full set of computed fields, and a REST fallback path. There is no contradiction with the annotations.

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?

The description is long but well-structured with clear sections, and the usage guidance is front-loaded. There is some redundancy with the input schema examples and the output field list, but the extra detail is relevant for correct invocation.

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?

For a calculator of this complexity, the description is complete: it covers purpose, exclusions, alternatives, inputs, output fields, formulas, boundary semantics, reference_year behavior, REST fallback, and documentation link. An agent has everything needed to invoke it correctly.

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 description coverage is 100%, so the baseline is 3. The description adds value by explaining how the boundary parameter changes the year calculation and how reference_year is used for age and 本命年 reporting. It mostly restates parameter types but clarifies their behavioral effect beyond the schema.

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 precise verb and resource: it finds the Chinese zodiac sign and element from a Gregorian birth date, including boundary handling and compatibility groups. It also explicitly distinguishes itself from full Bazi chart calculation and Western star signs, so an agent can clearly tell what this tool does.

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

Usage Guidelines5/5

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

It states exactly when to use the tool, when not to use it, and names the alternatives (bazi-four-pillars, zodiac). It also instructs the agent to call the tool directly rather than computing the answer from memory, which is strong usage guidance.

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

All Calcgrid toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources