Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Inner Animal (month branch)

astroway_chinese_zodiac_inner_animal
Read-onlyIdempotent

Calculate a Chinese zodiac inner animal from a birth date to reveal inner motivations and the private self. Supply date, time, and timezone for accurate results.

Instructions

Month-branch animal: represents inner motivations and private self.

[Group: Chinese: Zodiac & Feng Shui] [Endpoint: POST /v1/chinese/zodiac/inner-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_inner_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
glyphNo
descriptionNo
innerAnimalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description adds genuinely useful operational context not in annotations: the POST endpoint, the required 'date' input, and a 10-credit Tier 1 cost, which affects invocation decisions. It stops short of any behavioral detail about what the month-branch computation depends on (e.g., whether time/timezone shift the result).

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 purpose sentence is front-loaded and wastes no words, followed by compact machine-readable metadata lines (group, endpoint, required, cost). The metadata block is boilerplate rather than explanatory, but it does not bury the core statement.

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

Completeness2/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 described, but for a 6-parameter tool the description leaves four parameters unexplained and gives no guidance on precision requirements for a date/time-based Chinese calendrical computation. An agent could call it, but could easily supply wrong time/timezone semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only 2 of 6 parameters carry schema descriptions (33% coverage); 'date', 'time', 'language', and 'solarYear' are bare. The description contributes only '[Required: date]', which merely repeats the schema's required list, so it fails to compensate for the documentation gap on how time/timezone/solarYear affect the result.

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 names the specific artifact ('month-branch animal') and its interpretive meaning ('inner motivations and private self'), which is more than a restatement of the title. It does not, however, explicitly distinguish itself from close siblings such as astroway_chinese_zodiac_animal or astroway_chinese_zodiac_secret_animal, which also concern Chinese zodiac animals, leaving the agent to infer which animal layer it wants.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus the other Chinese zodiac tools (animal, secret animal, element, compatibility). The phrase 'inner motivations and private self' hints at a use case but gives no exclusions, prerequisites, or routing advice among a very crowded sibling set.

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