Feng Shui MCP Server by RoxyAPI

List Bagua sectors - Feng shui bagua map API

get_feng_shui_bagua

Read-only

The nine palaces of the compass Bagua map: the eight trigram sectors plus the centre, each with the life area it governs, its five phase, its colours, and both its Later Heaven and Earlier Heaven trigrams. This is the compass map aligned to true directions, so career is always North and wealth is always Southeast whichever way the entrance faces. Trigram details are served from the same source as the I-Ching trigram endpoints, so the two agree field for field. Built for floor plan overlays, room-by-room guides and any interface that maps a space onto life areas.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_feng_shui_bagua"
  }
}

Input 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
`limit`	No	Maximum items to return per page. Range: 1-9, default 9.
`offset`	No	Number of items to skip for pagination. Default 0.
`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

Name	Required	Description	Default
`limit`	Yes
`total`	Yes
`offset`	Yes
`sectors`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026
- addedInput schema / properties / offset / default
```
Added value: +0
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
Changed3 schema fields changedSep 20, 2026
- removedInput schema / properties / offset / default
```
Removed value: -0
```
- removedInput schema / properties / offset / minimum
```
Removed value: -0
```
- changedInput schema / properties / offset / type
```
Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"
```

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "limit": {
+      "type": "number"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "sectors": {
+      "items": {
+        "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"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "limit",
+    "offset",
+    "sectors"
+  ],
+  "type": "object"
+}

Changed4 schema fields changedSep 5, 2026

changedInput schema / properties / limit / default
```
Previous value: -20New value: +9
```

changedInput schema / properties / limit / description

Previous value: -"Maximum sectors to return per page. Range 1 to 9, default 20."New value: +"Maximum items to return per page. Range: 1-9, default 9."

changedInput schema / properties / limit / example
```
Previous value: -20New value: +9
```

changedInput schema / properties / offset / description

Previous value: -"Number of sectors to skip for pagination. Default 0."New value: +"Number of items to skip for pagination. Default 0."

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 the safety profile is covered. The description adds useful behavioral context: the map is aligned to true directions regardless of entrance facing, and trigram details are served from the same source as the I-Ching endpoints so they agree field for field. This gives the agent confidence about data semantics and consistency.

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 four sentences long, front-loads the core content, and contains no filler or repetition. Every sentence earns its place: what is returned, how it is aligned, consistency with I-Ching endpoints, and intended use cases.

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 list endpoint with zero required parameters and a full output schema, the description provides everything an agent needs: data content, semantic orientation, consistency guarantees, and use cases. The annotation already covers side effects, and the output schema covers return structure, 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 already documents lang, limit, offset, and compact in detail. The description does not add parameter-level meaning beyond what the schema provides, which matches the baseline for high coverage. No compensation is needed.

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 identifies exactly what is returned: the nine palaces of the compass Bagua map, each with life area, five phase, colours, and both Later and Earlier Heaven trigrams. It also distinguishes this tool from other feng shui endpoints by emphasizing the compass-aligned, direction-fixed nature of the map. The title and description together make the tool's scope unambiguous.

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 provides clear use cases: floor plan overlays, room-by-room guides, and any interface mapping a space onto life areas. It also clarifies that this is the compass map rather than one dependent on entrance facing. It does not explicitly name alternatives or say when not to use this tool, but the context is strong enough for an agent to route correctly.

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?