Skip to main content
Glama

Feng Shui MCP Server by RoxyAPI

by com.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
NameRequiredDescriptionDefault
kuaNoKua 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.
dateNoBirth 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.
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
facingNoOptional 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.
genderNoSelects the Kua formula variant. Required when the Kua is being derived from a birth date.
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.
yearBoundaryNoWhich 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

TDQS

A4.3/5.0
Behavior5/5

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

The description adds material behavior beyond the readOnlyHint annotation: sectors are returned ordered best to worst, each with a composed reading, and a ranking is included to decide which affliction to accept when no favorable sector is reachable. This meaningfully informs an agent about the return shape and the tool's logic.

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 front-loaded with the core deliverable and remains information-dense across four sentences. The enumeration of all eight star names lengthens it, but those names are domain-significant and help an agent recognize the tool's scope.

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?

For a tool with no output schema, the description covers the essential response behaviors: ordered sectors, per-sector readings, and an affliction-acceptance ranking. Combined with comprehensive schema documentation for language, compact shape, facing, and year boundary, a caller has nearly everything needed; only an explicit top-level response shape 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 baseline of 3 applies: the schema already documents every parameter in detail. The description adds a useful conceptual summary (Kua directly vs derived) but does not need to compensate for missing parameter documentation.

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 identifies the exact operation: it builds the complete Eight Mansions (Ba Zhai) map for a person, classifying all eight compass sectors into the four favorable and four unfavorable stars. It distinguishes itself from sibling feng shui tools by naming the specific domain, output, and use cases.

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 context ('Built for bed and desk placement tools, room-by-room reports and floor plan overlays') and describes the two input routes: direct Kua number or derivation from birth date and sex. It does not explicitly name sibling alternatives or exclusion conditions, so it stops short of a 5.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools target clearly distinct resources or calculations, but a few pairs could be confused from names alone: get_feng_shui_flying_stars (catalogue) vs the annual/monthly plates, and get_feng_shui_kua_number (lookup) vs post_feng_shui_kua (calculation). The descriptions resolve the ambiguity, so the overlap is minor.

Naming Consistency5/5

All 11 tool names follow the same snake_case pattern of {get|post}_feng_shui_<topic>, with the domain prefix consistently applied. The get/post split cleanly separates reference lookups from input-driven calculations, making the naming predictable and uniform.

Tool Count5/5

Eleven tools is well within the ideal 3–15 range and every tool earns its place, covering reference data, annual/monthly plates, personal calculations, and property-specific charts. The scope matches the domain without unnecessary redundancy or padding.

Completeness4/5

The surface covers the core Feng Shui domain thoroughly: afflictions, Bagua, flying stars, Kua, periods, Eight Mansions, and natal charts. Minor gaps exist, such as no dedicated date-selection/calendar tool or a 24-mountains reference, but agents can work around these with the existing endpoints.

Resources