Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Chinese Zodiac Animal

astroway_chinese_zodiac_animal
Read-onlyIdempotent

Determine the Chinese zodiac animal sign from a birth date, accounting for the exact Lichun solar-year boundary and returning the full stem-branch-element pillar.

Instructions

Animal sign of the birth year, bounded by the exact Lichun instant, plus the full pillar (stem + branch + element). yearStart and yearEnd are the two Lichun instants that bound the solar year, in UTC and Beijing time. Pass time + timezoneOffset for births on the boundary day.

[Group: Chinese: Zodiac & Feng Shui] [Endpoint: POST /v1/chinese/zodiac/animal] [Required: date] [Cost: 10 credits (Tier 1)]

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

Input Schema

NameRequiredDescriptionDefault
dateYes
timeNo
languageNo
timezoneNoIANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
solarYearNo
timezoneOffsetNoHours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

Output Schema

NameRequiredDescriptionDefault
stemNo
glyphNo
animalNo
branchNo
pillarNo
elementNo
yearEndNo
solarYearNo
yearStartNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.7/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 safety needs no restating. The description adds real value beyond them: the result is boundary-sensitive to the exact Lichun instant, and yearStart/yearEnd are returned in both UTC and Beijing time — the kind of determinism detail an agent cannot infer from annotations. Cost (10 credits, Tier 1) and endpoint are also disclosed. It stops short of describing error behavior for malformed dates.

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 behavior leads in the first sentence, with the boundary-handling caveat second and the metadata tags trailing. Every sentence earns its place; only the bracketed tag block is padding for a model that already receives parameters structurally.

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 present, the description need not explain return values, and it still clarifies the two boundary instants in a way the schema cannot. Required parameter, cost, and endpoint are covered. The one real gap is the unexplained `solarYear` override, which materially changes the computed animal.

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 coverage is only 33%, and the description compensates for just part of it: it explains why `time` and `timezoneOffset` matter (boundary-day births). `timezone` is already well documented in the schema. It says nothing about `solarYear` (an override of the year, unclear whether it replaces the year derived from `date`) or `language`, leaving two parameters undocumented in both places.

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?

States a specific verb-and-resource: it derives the birth-year animal sign plus the full year pillar (stem + branch + element), and pins the calculation to the exact Lichun instant. That is far more informative than the title alone. It does not, however, distinguish itself from near siblings such as astroway_bazi_year_pillar, astroway_chinese_zodiac_element, or astroway_chinese_zodiac_inner_animal, which an agent would need in order to route confidently.

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?

"Pass time + timezoneOffset for births on the boundary day" is a genuine conditional usage hint and the strongest guidance present. But there is no statement of when to choose this over the other Chinese/BaZi tools, and no exclusions or prerequisites beyond the required `date` tag.

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

Deploy Server

Other Tools