Skip to main content
Glama

Chinese zodiac

get_chinese_zodiac
Read-only

Gives the Chinese zodiac animal, element and yin or yang for a birth date or a year, and the current year's animal. It adds the animal's traditional associations and pairings (the harmonious three, the six-harmony partner and the opposite animal), with links to the animal's page. It fits a question about someone's Chinese zodiac animal, or the animal of a year. A birth date before that year's Lunar New Year belongs to the previous animal year, and the answer gives the Lunar New Year date it used. Years run from 1901 to 2100. Without a time zone the current year is worked out in UTC, and the answer says so. It refuses a full birth date less than 13 years ago; given only a year, it answers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_chinese_zodiac"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoA year, such as 1990, when the person gives only a year. The answer says which animal applies before that year's Lunar New Year.
zoneNoThe person's time zone, such as Asia/Singapore, so the current year is worked out for their own date. Without it, UTC.
birthDateNoThe birth date, such as 1990-01-20 (1901 to 2100). A date before that year's Lunar New Year belongs to the previous animal. Give this or year.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses non-obvious behavior: the Lunar New Year cutover for dates early in the year, the answer echoing the Lunar New Year date used, the 1901-2100 window, UTC as the implicit zone for current-year resolution with that assumption stated in the response, and a refusal policy for full birth dates under 13 years old. These are exactly the traits an agent cannot infer from 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?

The core capability and the input choice are front-loaded, and the constraint sentences are short and declarative. There is mild redundancy: the Lunar New Year boundary is stated twice (once as behavior, once inside the refusal/timezone sentences), which could be tightened.

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?

An output schema exists, so return values need not be spelled out, yet the description still tells the agent what the answer contains (the Lunar New Year date used, the UTC assumption). For a zero-required-parameter lookup with conditional refusal logic, everything needed to call it correctly is present.

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 parameters are already documented and 3 is the baseline. The description still adds meaning: it establishes that birthDate and year are alternatives ("Give this or year"), that a birthDate before the year's Lunar New Year maps to the prior animal, and that birthDate carries a privacy-driven rejection rule the schema does not mention.

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?

"Gives the Chinese zodiac animal, element and yin or yang for a birth date or a year" names a specific verb, the exact output fields, and the two accepted inputs. It goes on to name the added payload (traditional associations, three-harmony, six-harmony, opposite animal, page links), so an agent can tell this apart from the horoscope/natal-chart siblings without opening a 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 fits a question about someone's Chinese zodiac animal, or the animal of a year" gives an explicit positive trigger, and the 13-year refusal plus the 1901-2100 range set boundary conditions. What is missing is any negative routing ("for Western sun signs use get_horoscope"), so alternatives are left implicit.

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.