Skip to main content
Glama

Feng Shui MCP Server by RoxyAPI

by com.roxyapi

Look up a Bagua sector - Life area reference API

get_feng_shui_bagua_id
Read-only

Look up one palace of the compass Bagua map by its life area id, such as wealth, career or love. Returns the compass sector it occupies, its five phase and colours, both trigram arrangements and what the sector governs. The health palace is the centre and carries no direction and no trigram, because the centre of the Lo Shu is not a trigram.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesLife area id. One of career, knowledge, family, wealth, fame, love, children, helpful-people, health.
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
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.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the tool read-only and non-destructive. The description adds meaningful behavioral detail: what the response covers (sector, five phase, colours, trigram arrangements, governance) and the special exception that the health palace has no direction or trigram. This goes beyond what annotations alone convey.

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 two sentences with no filler. The main action and output are front-loaded, and the important edge case about the health palace is included compactly without derailing the primary definition.

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 single-lookup tool with fully documented parameters and read-only annotations, the description covers what is returned and the one noteworthy exception. There is no output schema, but the description compensates reasonably well by listing the returned data categories, making the tool safe and callable by an agent.

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 the id enum, lang defaults, and compact shape. The description only restates that the lookup is by life area id and adds no new parameter-level meaning, 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.

Purpose5/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 ('Look up one palace... by its life area id') and clarifies it is for a single sector rather than the whole Bagua map. This distinguishes it from the sibling get_feng_shui_bagua tool without needing to open the sibling schema.

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 context is clear: use this when you need one Bagua sector by life area id, not the full Bagua map. It does not name its sibling alternatives explicitly or give when-not-to-use conditions, but the single-palace scope makes the intended usage reasonably obvious.

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