Feng Shui MCP Server by RoxyAPI

Look up a Bagua sector - Life area reference API

get_feng_shui_bagua_id

Read-only

Look up one palace of the compass Bagua map by its life area id, such as wealth, career or love. Returns the compass sector it occupies, its five phase and colours, both trigram arrangements and what the sector governs. The health palace is the centre and carries no direction and no trigram, because the centre of the Lo Shu is not a trigram.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Life area id. One of career, knowledge, family, wealth, fame, love, children, helpful-people, health.
`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
`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
`id`	Yes
`name`	Yes
`focus`	Yes
`colors`	Yes
`number`	Yes
`palace`	Yes
`element`	Yes
`meaning`	Yes
`trigram`	No
`direction`	No
`nameLocalized`	No
`earlierHeavenTrigram`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "colors": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "direction": {
+      "type": "string"
+    },
+    "earlierHeavenTrigram": {
+      "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"
+    },
+    "element": {
+      "type": "string"
+    },
+    "focus": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "meaning": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "nameLocalized": {
+      "type": "string"
+    },
+    "number": {
+      "type": "number"
+    },
+    "palace": {
+      "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": [
+    "id",
+    "name",
+    "number",
+    "palace",
+    "element",
+    "colors",
+    "focus",
+    "meaning"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already mark this as read-only and non-destructive. The description adds useful behavioral context beyond that: it lists the returned data (compass sector, five phase, colours, trigram arrangements) and explicitly documents the health palace special case of having no direction or trigram. No contradiction 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 concise, front-loaded sentences with no filler. The first sentence defines the operation, the second summarizes the return payload, and the third documents the important exception. Every sentence earns its place.

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 simple single-lookup tool with full schema descriptions, read-only annotations, and an output schema available, the description is complete. It covers what the tool returns, the key input concept, and the notable health-palace exception. An agent has enough to invoke it 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 coverage is 100%, so the schema already documents id, lang, and compact. The description adds semantic value by explaining the 'id' selects a life area and by highlighting that 'health' behaves differently as the centre with no direction or trigram. This goes beyond the enum list in 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?

States a specific verb and resource: 'Look up one palace of the compass Bagua map by its life area id.' The description clearly scopes the tool to a single sector lookup, not the whole map, and gives concrete examples such as wealth, career, or love. This effectively distinguishes it from sibling tools like get_feng_shui_bagua.

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 clearly establishes when to use the tool: when you have a life area id and want details for one bagua palace. It does not explicitly name sibling alternatives or exclusions, but the 'one palace... by its life area id' framing gives enough context for an agent to select it appropriately.

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?