Feng Shui MCP Server by RoxyAPI

Calculate Kua number - Feng shui personal direction calculator API

post_feng_shui_kua

Read-only

Calculate the Kua number, also called the Ming Gua or life gua, from a birth date and sex. Returns the number, the east or west life group, the personal trigram, and all eight compass sectors classified from best to worst. The Chinese year is resolved at Li Chun by default, so an early February birthday is placed in the correct year rather than the calendar one, and the boundary that decided it is echoed back. Built for room and desk placement features, personalised feng shui reports, and any product that needs a favourable direction per person.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes	Birth date in YYYY-MM-DD format. Only the Chinese YEAR this date falls in enters the formula, so no birth time, latitude or longitude is needed. A January or early February birthday is the case that matters: it usually belongs to the PREVIOUS Chinese year and produces a different Kua. A date is read at the start of its day, and the boundary falls part-way through its own day, so a birth date landing exactly on the boundary day is placed in the outgoing year.
`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
`gender`	Yes	Selects the Kua formula variant. The two formulas are different arithmetic on the same year, and they also differ in where a raw result of 5 is reassigned.
`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.
`yearBoundary`	No	Which boundary starts the Chinese year. Defaults to li-chun, the astronomical start of spring in early February, which is the classical position and the one feng shui uses for periods, annual stars and afflictions alike. Send lunar-new-year to match popular zodiac tables, which start the year two to four weeks later. The two disagree for anyone born between the two dates.	li-chun

TDQS

A4.1/5.0

Behavior5/5

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

The description reveals a non-obvious behavioral detail: the Chinese year is resolved at Li Chun, early February birthdays are placed in the correct year, and the boundary that decided the year is echoed back. This adds meaningful context beyond the readOnlyHint and destructiveHint annotations without contradicting them.

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 three sentences and front-loaded: core function and outputs first, edge-case behavior second, use cases third. Every sentence contributes, though the final use-case sentence is somewhat generic.

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?

With no output schema, the description compensates by listing the return data and clarifying the Li Chun boundary behavior. Parameter options like lang, compact, and yearBoundary are covered in the schema, so an agent has enough to invoke the tool correctly.

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?

The input schema has 100% coverage with detailed descriptions for date, gender, lang, compact, and yearBoundary. The description adds no additional parameter-level semantics, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Calculate the Kua number') and enumerates the return values: number, life group, trigram, and eight compass sectors. However, it does not explicitly distinguish itself from the sibling tool get_feng_shui_kua_number, so it is clear but not fully differentiated.

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 final sentence gives concrete use contexts: 'room and desk placement features, personalised feng shui reports, and any product that needs a favourable direction per person.' This is clear context but there is no when-not-to-use guidance or mention of alternatives among the feng shui siblings.

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

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

Need Help?