Skip to main content
Glama

AstroWay Astrology API (full catalogue)

Inner Animal (month branch)

astroway_chinese_zodiac_inner_animal
Read-onlyIdempotent

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
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
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.
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
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. Changed6 schema fields changed
    • removedOutput schema / properties / description / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / description / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / glyph / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / glyph / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / innerAnimal / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / innerAnimal / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful operational facts the annotations lack — the POST endpoint and a cost of 10 credits (Tier 1) — but says nothing about which inputs actually affect the result (e.g. whether time of day matters) or how the animal is derived.

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 substantive sentence is front-loaded and wastes no words, and the bracketed metadata (group, endpoint, required, cost) is scannable. A small deduction because the tag block occupies more space than the actual explanation, leaving the definition top-heavy on boilerplate.

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

Completeness3/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 no explanation, and the cost/endpoint tags round out the operational picture. Still, for a calc tool with 8 parameters and ambiguous sibling overlap, the description leaves important questions unanswered — chiefly how it differs from the year/secret animal tools and whether time and timezone affect the computation.

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 'Required: date' is mentioned, which merely repeats the schema's required array. With 8 parameters and only 50% schema description coverage, five parameters (date, time, language, solarYear, and the relationship between timezone and timezoneOffset) receive no meaning from the description, notably whether time influences the month branch at a boundary.

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 a specific resource — the month-branch animal of the Chinese zodiac — and states its meaning ('inner motivations and private self'), which is more than a restatement of the tool name. It stops short of explicitly contrasting with the closely related siblings astroway_chinese_zodiac_animal (year animal) and astroway_chinese_zodiac_secret_animal (hour animal), so an agent must infer the branch distinction.

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 guidance on when to choose this over the year animal, secret animal, or element tools in the same group. The only selection hint is the parenthetical 'month branch', which is implicit rather than an explicit when-to-use rule, and no prerequisites or exclusions are given.

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.

Resources