Skip to main content
Glama

Feng Shui MCP Server by RoxyAPI

by com.roxyapi
OverviewDiscussionsAdmin

Look up a Kua number - Eight Mansions reference API

get_feng_shui_kua_number
Read-only

Look up the reference chart for one Kua number: its trigram, its east or west life group, and how it classifies all eight compass sectors. A pure reference endpoint with no birth data required, for building a lookup table or a picker. Number 5 is served for completeness and is never a computed result, because it belongs to the centre and has no direction of its own: a man whose formula gives 5 reads Kua 2 and a woman reads Kua 8, and the chart returned for 5 is therefore the Kua 2 chart.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoResponse 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
numberYesKua number, 1 to 9.
compactNoSet 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
NameRequiredDescriptionDefault
groupYes
numberYes
sectorsYes
trigramYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "group": {
+      "type": "string"
+    },
+    "number": {
+      "type": "number"
+    },
+    "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"
+    },
+    "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": [
+    "number",
+    "group",
+    "trigram",
+    "sectors"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / number / type
      Previous value: -"number"New value: +"integer"
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark it read-only and non-destructive, and the description adds substantial non-obvious behavior: Kua 5 is never a computed result, belongs to the centre, and the chart returned for 5 is the Kua 2 chart. It also explains the man/woman substitution rule, which is valuable context beyond 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 opens with the core purpose and outputs, then gives usage context, then the edge case. Every sentence earns its place, and there is no filler or repetition of schema details. The long third sentence is dense but directly relevant.

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 an output schema present, the description does not need to spell out the return shape. It provides the lookup context, the no-birth-data distinction, and the critical Kua-5 edge case, making it complete for an agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds extra semantics for the `number` parameter that the schema lacks, specifically the special meaning of 5 and its mapping to the Kua 2 chart. This is meaningful value beyond the schema.

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 verb ('Look up') and resource ('the reference chart for one Kua number'), and enumerates the returned contents: trigram, east/west life group, and all eight compass sectors. It also distinguishes itself from computation-oriented siblings by labeling itself a 'pure reference endpoint' with no birth data required.

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?

It gives concrete use cases ('building a lookup table or a picker') and explicitly says no birth data is required, which implies a computation endpoint should be used when birth data is present. However, it does not name the sibling computation tool directly or state a clear 'do not use when...' condition.

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 toolsInspect
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