Skip to main content
Glama

Get Chinese Astrology

Chinese zodiac year

get_zodiac_year
Read-onlyIdempotent

Returns the Chinese zodiac year for a birth date or a calendar year: the animal, Heavenly Stem, element, yin or yang, the Chinese New Year dates that open and close the year and the Li Chun date. A birth date also reports whether Chinese New Year and Li Chun give different animals.

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_zodiac_year"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoBirth date as YYYY-MM-DD, from 1901-02-19 to 2100-02-08. The year can be given instead.
yearNoZodiac year from 1901 to 2099, opened by Chinese New Year of that year. The date can be given instead.

Output Schema

NameRequiredDescriptionDefault
itemYes
viewYes
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, closed-world tool. The description adds meaningful behavioral context beyond that: it explains the data returned and the special birth-date behavior around Chinese New Year versus Li Chun. It does not discuss error handling or edge cases, but the annotations cover the main safety profile.

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 compact and front-loaded: it names the operation first, then lists the result fields, then calls out the birth-date-specific distinction. Every sentence contributes, though the long enumeration of output fields is somewhat dense.

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 an output schema, full schema descriptions, and rich annotations, the description is nearly complete. The only notable gap is that it does not explicitly state what happens if both or neither of the optional parameters are supplied, leaving a small ambiguity around parameter selection.

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%, and the schema already documents both parameters, including date format, valid ranges, and the relationship between date and year. The description restates that either a birth date or calendar year can be supplied but adds little meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource ('Returns the Chinese zodiac year') and then enumerates the returned components: animal, Heavenly Stem, element, yin/yang, Chinese New Year dates, and Li Chun date. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools such as get_bazi_chart or check_animal_compatibility.

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

Usage Guidelines3/5

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

The description identifies two input modes—birth date or calendar year—and notes that a birth date additionally reports whether Chinese New Year and Li Chun produce different animals. However, it does not give explicit when-to-use guidance, exclusions, or direct alternatives for cases such as compatibility checks or full BaZi charts.

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.