Chinese Astrology MCP Server by RoxyAPI

List the five elements - Wu Xing API with generating and controlling cycles

get_chinese_astrology_elements

Read-only

Return the five phases of Wu Xing with the Chinese character, the season and direction each governs, the Heavenly Stems and Earthly Branches that carry it, and both of the cycles that connect them. The generating cycle and the controlling cycle are returned as ordered rings as well as on each phase, so a caller can render either without deriving it. This is the one place the five phase vocabulary is defined: BaZi charts, Na Yin, zodiac element variants and every feng shui star reuse these identifiers rather than restating them.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English.	en
`limit`	No	Maximum items to return per page. Range: 1-5, default 5.
`offset`	No	Number of items to skip for pagination. Default 0.
`compact`	No	Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	Yes
`total`	Yes
`offset`	Yes
`elements`	Yes
`generatingCycle`	Yes
`controllingCycle`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026
- addedInput schema / properties / offset / default
```
Added value: +0
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
Changed3 schema fields changedSep 20, 2026
- removedInput schema / properties / offset / default
```
Removed value: -0
```
- removedInput schema / properties / offset / minimum
```
Removed value: -0
```
- changedInput schema / properties / offset / type
```
Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"
```

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "controllingCycle": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "elements": {
+      "items": {
+        "properties": {
+          "branches": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "chinese": {
+            "type": "string"
+          },
+          "controlledBy": {
+            "type": "string"
+          },
+          "controls": {
+            "type": "string"
+          },
+          "direction": {
+            "type": "string"
+          },
+          "generatedBy": {
+            "type": "string"
+          },
+          "generates": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "meaning": {
+            "type": "string"
+          },
+          "nameLocalized": {
+            "type": "string"
+          },
+          "pinyin": {
+            "type": "string"
+          },
+          "season": {
+            "type": "string"
+          },
+          "stems": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "id",
+          "chinese",
+          "pinyin",
+          "season",
+          "direction",
+          "generates",
+          "generatedBy",
+          "controls",
+          "controlledBy",
+          "stems",
+          "branches",
+          "meaning"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "generatingCycle": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "limit": {
+      "type": "number"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "limit",
+    "offset",
+    "generatingCycle",
+    "controllingCycle",
+    "elements"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds real behavioral detail: generating and controlling cycles are returned both as ordered rings and per phase, so a caller can render without deriving; the uniqueness of the vocabulary is useful context. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each earning its place: the first enumerates contents, the second explains the cycle representation and its benefit, the third gives selection context. No filler or repetition of schema details.

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?

With a full output schema and annotations covering the read-only safety profile, the description covers every behavioral aspect an agent needs: itemized return content, cycle representation, and the tool's role in the API family. The optional parameters are all documented in the schema.

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%, so the schema fully documents lang, limit, offset, and compact; the baseline of 3 applies. The description itself adds nothing parameter-specific, but it does not need to.

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?

States a specific verb ('Return') and resource ('the five phases of Wu Xing') with a detailed list of returned attributes, plus the two cycles. The final sentence differentiates it from all sibling tools by describing it as the canonical definition point for five-phase identifiers.

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?

The description tells an agent this is the single source for five-phase vocabulary, so it should be selected over sibling tools when canonical element identifiers or cycles are needed. It does not list explicit exclusions or compare directly to named siblings, stopping one step short of the highest bar.

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

All Chinese Astrology MCP Server by RoxyAPI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?