Skip to main content
Glama

Feng Shui MCP Server by RoxyAPI

by com.roxyapi

Generate flying star natal chart - Xuan Kong Fei Xing API

post_feng_shui_flying_stars_natal
Read-only

Cast the Xuan Kong flying star natal chart for a building from its construction period and the direction it faces. Returns all nine palaces with the period star, the mountain star that governs health and relationships and the water star that governs wealth, plus the named formation and a composed reading for every palace, and the classical verdict on how the two prosperous stars landed. Facing is accepted as one of the 24 mountains or as a compass bearing. Built for property analysis tools, floor plan overlays and consultation software.

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
facingNoThe mountain the front of the building faces, by id or by compass label such as S2. Send this or facingDegrees, not neither. The facing side is the open, active, public side, which is not always the side with the front door.
periodNoConstruction period of the building, 1 to 9. This is the twenty year cycle the building was completed in, or last renovated heavily enough to reset, and it is fixed for the life of the building. Periods change at Li Chun in early February, so a building finished in January 2024 is a Period 8 building. Defaults to the period in force now.
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.
facingDegreesNoThe compass bearing the front of the building faces, 0 to 360 degrees, measured looking out from inside. Resolved to one of the 24 mountains. Send this or facing, not neither.

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 no safety contradiction exists. The description adds meaningful behavioral detail by explaining exactly what the read-only operation returns: nine palaces, period/mountain/water stars, formations, per-palace readings, and the prosperous-stars verdict. This goes beyond the structured annotations and gives the agent a concrete picture of the output.

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 dense but every sentence earns its place: purpose, output composition, accepted facing format, and intended use context. It is front-loaded with the primary verb and resource, and the final sentence usefully identifies the audience without padding.

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?

Given the domain complexity and the absence of an output schema, the description does an excellent job of telling the agent what to expect: all nine palaces, the three star types, the named formation, per-palace readings, and the classical verdict. Combined with the fully documented input schema, the tool definition is complete enough for correct selection and invocation.

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%, and every parameter already has rich guidance: facing vs facingDegrees exclusivity, period semantics including Li Chun, language defaults, and compact format behavior. The description only lightly restates that facing is accepted as 24 mountains or a compass bearing, adding no new parameter meaning beyond what the schema already provides.

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 opens with a precise verb, 'Cast', and names the exact resource: the Xuan Kong flying star natal chart. It also specifies the two determining inputs, construction period and facing direction, and lists the output contents in detail. The word 'natal' clearly distinguishes it from the annual and monthly flying star tools among the siblings.

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 gives clear context for when the tool applies: natal charts for buildings, driven by period and facing, aimed at property analysis, overlays, and consultation software. It does not explicitly instruct the agent to use the sibling annual/monthly tools for different time scopes, so it stops short of full when-not guidance.

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