Feng Shui MCP Server by RoxyAPI

Calculate Kua number - Feng shui personal direction calculator API

post_feng_shui_kua

Read-only

Calculate the Kua number, also called the Ming Gua or life gua, from a birth date and sex. Returns the number, the east or west life group, the personal trigram, and all eight compass sectors classified from best to worst. The Chinese year is resolved at Li Chun by default, so an early February birthday is placed in the correct year rather than the calendar one, and the boundary that decided it is echoed back. Built for room and desk placement features, personalised feng shui reports, and any product that needs a favourable direction per person.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes	Birth date in YYYY-MM-DD format. Only the Chinese YEAR this date falls in enters the formula, so no birth time, latitude or longitude is needed. A January or early February birthday is the case that matters: it usually belongs to the PREVIOUS Chinese year and produces a different Kua. A date is read at the start of its day, and the boundary falls part-way through its own day, so a birth date landing exactly on the boundary day 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
`gender`	Yes	Selects the Kua formula variant. The two formulas are different arithmetic on the same year, and they also differ in where a raw result of 5 is reassigned.
`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. Defaults to li-chun, the astronomical start of spring in early February, which is the classical position and the one feng shui uses for periods, annual stars and afflictions alike. Send lunar-new-year to match popular zodiac tables, which start the year two to four weeks later. The two disagree for anyone born between the two dates.	li-chun

Output Schema

TableJSON Schema

Name	Required	Description	Default
`kua`	Yes
`group`	Yes
`gender`	Yes
`rawKua`	Yes
`sectors`	Yes
`trigram`	Yes
`solarYear`	Yes
`reassigned`	Yes
`conventions`	Yes
`boundaryDate`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "boundaryDate": {
+      "type": "string"
+    },
+    "conventions": {
+      "properties": {
+        "yearBoundary": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "yearBoundary"
+      ],
+      "type": "object"
+    },
+    "gender": {
+      "type": "string"
+    },
+    "group": {
+      "type": "string"
+    },
+    "kua": {
+      "type": "number"
+    },
+    "rawKua": {
+      "type": "number"
+    },
+    "reassigned": {
+      "type": "boolean"
+    },
+    "sectors": {
+      "items": {
+        "properties": {
+          "direction": {
+            "type": "string"
+          },
+          "domain": {
+            "type": "string"
+          },
+          "nature": {
+            "type": "string"
+          },
+          "rank": {
+            "type": "number"
+          },
+          "star": {
+            "type": "string"
+          },
+          "starName": {
+            "type": "string"
+          },
+          "starNameLocalized": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "direction",
+          "star",
+          "starName",
+          "nature",
+          "rank",
+          "domain"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "solarYear": {
+      "type": "number"
+    },
+    "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": [
+    "kua",
+    "rawKua",
+    "reassigned",
+    "gender",
+    "group",
+    "solarYear",
+    "boundaryDate",
+    "trigram",
+    "sectors",
+    "conventions"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already mark the tool as read-only and non-destructive, so the safety profile is covered. The description adds valuable behavioral context: the boundary being 'echoed back' and the edge-case handling of early February birthdays (placed in previous year). It also clarifies that date resolution is at day start, with the boundary day falling in the outgoing year. This goes beyond annotations and provides meaningful behavioral detail for an API with no side effects.

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 description is two sentences, front-loaded with the core purpose. The first sentence states the action and outputs, and the second explains the key behavioral nuance (Li Chun resolution) and use cases. It is concise and well-structured, with no fluff. It could be slightly more concise by dropping 'personalised' duplication, but it's well within acceptable limits.

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?

Given the tool's moderate complexity (5 parameters, 3 enums, output schema present), the description is sufficiently complete. It doesn't need to explain return values because an output schema exists. It covers why parameters like date and yearBoundary have edge cases, and mentions the boundary echo, which is a subtle behavior. Combined with the detailed schema, an agent has enough information to call this tool correctly. The only minor gap is that it doesn't explicitly state how the compact format works, but that's a schema concern, not a description gap.

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 coverage is 100%, with detailed parameter descriptions for each field (e.g., date format, gender affecting formula, yearBoundary differences). The description adds context on the date parameter by explaining why only the Chinese year matters and highlighting the boundary edge case, which is helpful. However, it doesn't add semantics for 'lang', 'compact', or 'yearBoundary' beyond what the schema already states. The description focuses on the date parameter's significance, providing slight added value, but generally the schema handles most of the load, so a baseline of 3 is appropriate.

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 clearly states the verb 'Calculate' and the resource 'Kua number' (also known as Ming Gua or life gua). It lists specific outputs (number, life group, trigram, compass sectors) and elaborates on the Chinese year resolution (Li Chun boundary), which distinguishes it from any calendar-year-based tool. This differentiates it from siblings like get_feng_shui_kua_number (which is likely a getter for a list or a different endpoint) and other calculation 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 conveys clear use cases: 'Built for room and desk placement features, personalised feng shui reports, and any product that needs a favourable direction per person.' While it doesn't explicitly mention when NOT to use it or reference sibling alternatives, the distinct purpose and mention of Li Chun default (contrasting with lunar-new-year) give context for typical usage. It lacks explicit exclusion of scenarios like when only a zodiac year is needed.

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?