Skip to main content
Glama

Feng Shui MCP Server by 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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
facingYes
periodYes
palacesYes
sittingYes
structureYes
straddlingYes
waterFlightYes
facingDegreesNo
mountainFlightYes
waterCenterStarYes
mountainCenterStarYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "facing": {
      +      "properties": {
      +        "chinese": {
      +          "type": "string"
      +        },
      +        "direction": {
      +          "type": "string"
      +        },
      +        "endDegree": {
      +          "type": "number"
      +        },
      +        "id": {
      +          "type": "string"
      +        },
      +        "label": {
      +          "type": "string"
      +        },
      +        "pinyin": {
      +          "type": "string"
      +        },
      +        "polarity": {
      +          "type": "string"
      +        },
      +        "startDegree": {
      +          "type": "number"
      +        },
      +        "yuan": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "label",
      +        "chinese",
      +        "pinyin",
      +        "direction",
      +        "yuan",
      +        "polarity",
      +        "startDegree",
      +        "endDegree"
      +      ],
      +      "type": "object"
      +    },
      +    "facingDegrees": {
      +      "type": "number"
      +    },
      +    "mountainCenterStar": {
      +      "type": "number"
      +    },
      +    "mountainFlight": {
      +      "type": "string"
      +    },
      +    "palaces": {
      +      "items": {
      +        "properties": {
      +          "base": {
      +            "type": "number"
      +          },
      +          "combination": {
      +            "properties": {
      +              "chinese": {
      +                "type": "string"
      +              },
      +              "id": {
      +                "type": "string"
      +              },
      +              "name": {
      +                "type": "string"
      +              },
      +              "nameLocalized": {
      +                "type": "string"
      +              },
      +              "nature": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "id",
      +              "name",
      +              "nature"
      +            ],
      +            "type": "object"
      +          },
      +          "mountain": {
      +            "type": "number"
      +          },
      +          "palace": {
      +            "type": "string"
      +          },
      +          "period": {
      +            "type": "number"
      +          },
      +          "reading": {
      +            "type": "string"
      +          },
      +          "water": {
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "palace",
      +          "base",
      +          "period",
      +          "mountain",
      +          "water",
      +          "reading"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "period": {
      +      "type": "number"
      +    },
      +    "sitting": {
      +      "properties": {
      +        "chinese": {
      +          "type": "string"
      +        },
      +        "direction": {
      +          "type": "string"
      +        },
      +        "endDegree": {
      +          "type": "number"
      +        },
      +        "id": {
      +          "type": "string"
      +        },
      +        "label": {
      +          "type": "string"
      +        },
      +        "pinyin": {
      +          "type": "string"
      +        },
      +        "polarity": {
      +          "type": "string"
      +        },
      +        "startDegree": {
      +          "type": "number"
      +        },
      +        "yuan": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "label",
      +        "chinese",
      +        "pinyin",
      +        "direction",
      +        "yuan",
      +        "polarity",
      +        "startDegree",
      +        "endDegree"
      +      ],
      +      "type": "object"
      +    },
      +    "straddling": {
      +      "type": "boolean"
      +    },
      +    "structure": {
      +      "properties": {
      +        "chinese": {
      +          "type": "string"
      +        },
      +        "id": {
      +          "type": "string"
      +        },
      +        "meaning": {
      +          "type": "string"
      +        },
      +        "name": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "name",
      +        "chinese",
      +        "meaning"
      +      ],
      +      "type": "object"
      +    },
      +    "waterCenterStar": {
      +      "type": "number"
      +    },
      +    "waterFlight": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "period",
      +    "facing",
      +    "sitting",
      +    "straddling",
      +    "mountainCenterStar",
      +    "waterCenterStar",
      +    "mountainFlight",
      +    "waterFlight",
      +    "structure",
      +    "palaces"
      +  ],
      +  "type": "object"
      +}
  2. First observed

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, and the description adds meaningful behavioral detail: it returns all nine palaces, the period/mountain/water stars, named formations, a composed reading, and the classical verdict. This gives the agent a strong picture of what the tool produces beyond the structured 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 is three sentences with no wasted words: it states the operation, summarizes the rich output, and covers accepted facing inputs plus intended use cases. Every sentence earns its place and the core action is front-loaded.

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 rich input schema, output schema, and safety annotations, the description is complete enough for an agent to select and invoke this tool correctly. It covers inputs, output meaning, domain context, and target use cases; the either/or facing/facingDegrees requirement is already fully documented in the parameter descriptions.

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 applies and the input schema already documents period, facing, facingDegrees, compact, and lang. The description adds useful domain context about mountain stars governing health/relationships and water stars governing wealth, but it does not substantially clarify parameter mechanics 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 specific verb and resource: 'Cast the Xuan Kong flying star natal chart for a building' from construction period and facing direction. It clearly distinguishes this natal-chart tool from the annual and monthly flying star siblings by emphasizing construction period, facing, and the nine-palace natal output.

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 is appropriate: natal chart calculation for a building, intended for property analysis tools, floor plan overlays, and consultation software. It does not explicitly name sibling tools as alternatives or state when not to use it, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources