Feng Shui MCP Server by RoxyAPI

Generate Eight Mansions map - Ba Zhai lucky direction API

post_feng_shui_eight_mansions

Read-only

Build the full Eight Mansions (Ba Zhai) map for a person: all eight compass sectors classified into the four favourable stars, Sheng Chi, Tian Yi, Yan Nian and Fu Wei, and the four unfavourable ones, Huo Hai, Wu Gui, Liu Sha and Jue Ming. Sectors come back ordered best to worst with a composed reading each, plus the ranking that decides which affliction to accept when no favourable sector is reachable. Accepts a Kua number directly or derives one from a birth date and sex. Built for bed and desk placement tools, room-by-room reports and floor plan overlays.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kua`	No	Kua number to build the map for, if you already have one. Send this OR date and gender, not neither. A Kua of 5 is read as the Kua 2 chart, since 5 has no direction of its own.
`date`	No	Birth date in YYYY-MM-DD format, used to derive the Kua when no kua is sent. Requires gender alongside it. A date is read at the start of its day, so a birth date landing exactly on the year boundary is placed in the outgoing year.
`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
`facing`	No	Optional compass sector the main door faces, one of North, Northeast, East, Southeast, South, Southwest, West, Northwest. When sent, the response names the star sitting on that sector so a caller can judge an entrance without scanning the whole map.
`gender`	No	Selects the Kua formula variant. Required when the Kua is being derived from a birth date.
`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.
`yearBoundary`	No	Which boundary starts the Chinese year when the Kua is derived from a birth date. Defaults to li-chun, the classical position. Ignored when a kua is sent directly, and echoed back either way.	li-chun

Output Schema

TableJSON Schema

Name	Required	Description	Default
`kua`	Yes
`group`	Yes
`sectors`	Yes
`trigram`	Yes
`bestSector`	Yes
`conventions`	Yes
`worstSector`	Yes
`facingSector`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "bestSector": {
+      "type": "string"
+    },
+    "conventions": {
+      "properties": {
+        "yearBoundary": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "yearBoundary"
+      ],
+      "type": "object"
+    },
+    "facingSector": {
+      "properties": {
+        "direction": {
+          "type": "string"
+        },
+        "nature": {
+          "type": "string"
+        },
+        "star": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "direction",
+        "star",
+        "nature"
+      ],
+      "type": "object"
+    },
+    "group": {
+      "type": "string"
+    },
+    "kua": {
+      "type": "number"
+    },
+    "sectors": {
+      "items": {
+        "properties": {
+          "chinese": {
+            "type": "string"
+          },
+          "direction": {
+            "type": "string"
+          },
+          "domain": {
+            "type": "string"
+          },
+          "nature": {
+            "type": "string"
+          },
+          "pinyin": {
+            "type": "string"
+          },
+          "rank": {
+            "type": "number"
+          },
+          "reading": {
+            "type": "string"
+          },
+          "star": {
+            "type": "string"
+          },
+          "starName": {
+            "type": "string"
+          },
+          "starNameLocalized": {
+            "type": "string"
+          },
+          "trigram": {
+            "properties": {
+              "binary": {
+                "type": "string"
+              },
+              "chinese": {
+                "type": "string"
+              },
+              "direction": {
+                "type": "string"
+              },
+              "directionLocalized": {
+                "type": "string"
+              },
+              "element": {
+                "type": "string"
+              },
+              "elementLocalized": {
+                "type": "string"
+              },
+              "english": {
+                "type": "string"
+              },
+              "familyMember": {
+                "type": "string"
+              },
+              "nameLocalized": {
+                "type": "string"
+              },
+              "number": {
+                "type": "number"
+              },
+              "pinyin": {
+                "type": "string"
+              },
+              "symbol": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "number",
+              "chinese",
+              "english",
+              "pinyin",
+              "symbol",
+              "binary",
+              "element",
+              "direction",
+              "familyMember"
+            ],
+            "type": "object"
+          }
+        },
+        "required": [
+          "direction",
+          "star",
+          "starName",
+          "chinese",
+          "pinyin",
+          "nature",
+          "rank",
+          "domain",
+          "trigram",
+          "reading"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "trigram": {
+      "properties": {
+        "binary": {
+          "type": "string"
+        },
+        "chinese": {
+          "type": "string"
+        },
+        "direction": {
+          "type": "string"
+        },
+        "directionLocalized": {
+          "type": "string"
+        },
+        "element": {
+          "type": "string"
+        },
+        "elementLocalized": {
+          "type": "string"
+        },
+        "english": {
+          "type": "string"
+        },
+        "familyMember": {
+          "type": "string"
+        },
+        "nameLocalized": {
+          "type": "string"
+        },
+        "number": {
+          "type": "number"
+        },
+        "pinyin": {
+          "type": "string"
+        },
+        "symbol": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "number",
+        "chinese",
+        "english",
+        "pinyin",
+        "symbol",
+        "binary",
+        "element",
+        "direction",
+        "familyMember"
+      ],
+      "type": "object"
+    },
+    "worstSector": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "kua",
+    "group",
+    "trigram",
+    "sectors",
+    "bestSector",
+    "worstSector",
+    "conventions"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.2/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, and the description adds meaningful behavioral detail: sectors are returned ordered best-to-worst, each with a composed reading, plus a ranking that decides which affliction to accept. It also clarifies that a Kua may be supplied or derived, adding context without contradicting the 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?

The description is information-dense and each sentence earns its place: the core purpose, the ordered output shape, and the derivation/use-case context. The main action is front-loaded before the star-name details.

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?

Together with a rich input schema and output schema, the description gives an agent enough context to select and invoke the tool correctly: it explains the output substance, input modes, and intended applications. It does not repeat parameter constraints like the mutual-exclusion of kua vs date+gender, but those are already explicitly covered 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 already documents all parameter meaning. The description only summarizes the Kua-or-birth-date/gender choice already described in the schema and adds no new parameter-level semantics, matching the baseline of 3.

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 starts with a specific verb and resource: 'Build the full Eight Mansions (Ba Zhai) map for a person,' then enumerates the four favorable and four unfavorable stars. This clearly distinguishes it from sibling tools like flying stars, bagua, or Kua-number-only 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 explicitly names target use cases: 'Built for bed and desk placement tools, room-by-room reports and floor plan overlays.' It does not name sibling alternatives or give an explicit when-not-to-use condition, so it stops short of full usage guidance.

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

All Feng Shui 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?