Chinese Astrology MCP Server by RoxyAPI

Chinese zodiac compatibility - Trine, six harmony, clash and harm analysis

get_chinese_astrology_zodiac_compatibility_sign1_sign2

Read-only

Score and explain the relationship between two Chinese zodiac animals from the classical branch relations rather than from a lookup table of opinions. Returns which of the six relations the pair stands in, a score out of 100, the phase the two branches combine into where they combine at all, and a composed reading with strengths, frictions and advice. The six relations are mutually exclusive by construction, so exactly one applies to any pair. Built for matchmaking features, relationship reports and compatibility widgets.

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
`sign1`	Yes	First animal id, case-insensitive. One of rat, ox, tiger, rabbit, dragon, snake, horse, goat, monkey, rooster, dog, pig.
`sign2`	Yes	Second animal id, case-insensitive. The relation is symmetric, so swapping the two returns the same relationship and the same score, with the reading written from the first sign point of view.
`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
`score`	Yes
`signs`	Yes
`advice`	Yes
`summary`	Yes
`verdict`	Yes
`frictions`	Yes
`strengths`	Yes
`relationship`	Yes
`sharedElement`	No
`relationshipName`	Yes
`relationshipPinyin`	Yes
`relationshipChinese`	Yes
`sharedElementLocalized`	No
`relationshipNameLocalized`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "advice": {
+      "type": "string"
+    },
+    "frictions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "relationship": {
+      "type": "string"
+    },
+    "relationshipChinese": {
+      "type": "string"
+    },
+    "relationshipName": {
+      "type": "string"
+    },
+    "relationshipNameLocalized": {
+      "type": "string"
+    },
+    "relationshipPinyin": {
+      "type": "string"
+    },
+    "score": {
+      "type": "number"
+    },
+    "sharedElement": {
+      "type": "string"
+    },
+    "sharedElementLocalized": {
+      "type": "string"
+    },
+    "signs": {
+      "properties": {
+        "first": {
+          "properties": {
+            "branch": {
+              "type": "string"
+            },
+            "chinese": {
+              "type": "string"
+            },
+            "element": {
+              "type": "string"
+            },
+            "elementLocalized": {
+              "type": "string"
+            },
+            "id": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "nameLocalized": {
+              "type": "string"
+            },
+            "pinyin": {
+              "type": "string"
+            },
+            "polarity": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "id",
+            "name",
+            "chinese",
+            "pinyin",
+            "branch",
+            "element",
+            "polarity"
+          ],
+          "type": "object"
+        },
+        "second": {
+          "properties": {
+            "branch": {
+              "type": "string"
+            },
+            "chinese": {
+              "type": "string"
+            },
+            "element": {
+              "type": "string"
+            },
+            "elementLocalized": {
+              "type": "string"
+            },
+            "id": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "nameLocalized": {
+              "type": "string"
+            },
+            "pinyin": {
+              "type": "string"
+            },
+            "polarity": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "id",
+            "name",
+            "chinese",
+            "pinyin",
+            "branch",
+            "element",
+            "polarity"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "first",
+        "second"
+      ],
+      "type": "object"
+    },
+    "strengths": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "verdict": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "signs",
+    "relationship",
+    "relationshipName",
+    "relationshipChinese",
+    "relationshipPinyin",
+    "score",
+    "verdict",
+    "summary",
+    "strengths",
+    "frictions",
+    "advice"
+  ],
+  "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, so safety is covered. The description adds useful behavioral context: the six relations are mutually exclusive, exactly one applies, and results are computed from classical branch relations rather than opinion lookup tables. This goes beyond what annotations alone convey.

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 dense sentences with no filler. The action and return value are front-loaded, the behavioral guarantee about mutually exclusive relations earns its place, and the intended use cases are stated compactly at the end.

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?

For a read-only compatibility tool with an output schema, the description covers what it does, what it returns, how it computes results, and when to use it. The symmetric-relation note lives in the schema, and the output schema handles return details, so nothing essential is missing.

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 sign1, sign2, lang, and compact. The tool description does not add parameter-level detail, but that is not necessary here; it remains at the baseline 3 because the schema carries the semantic load.

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?

The description states a specific action ('Score and explain'), a specific resource ('relationship between two Chinese zodiac animals'), and a distinctive method ('classical branch relations rather than from a lookup table of opinions'). It also enumerates concrete outputs, so an agent can distinguish it from sibling bazi compatibility and zodiac animal tools.

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 gives clear intended contexts: 'matchmaking features, relationship reports and compatibility widgets'. It does not explicitly name alternatives or say when not to use this tool, but the use-case framing is enough for typical selection among the zodiac-related siblings.

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?