Feng Shui MCP Server by RoxyAPI

Monthly flying stars - Month by month feng shui overlay API

get_feng_shui_flying_stars_monthly

Read-only

Return the monthly flying star plate, the faster overlay that sits on top of the annual one. Months here are SOLAR months: month 1 begins at Li Chun in early February and each month begins at the next of the twelve major solar terms, so they never line up with calendar months. Omit both parameters to get the month in progress. Built for monthly guidance features and for timing work around an affliction that only lands for part of the year.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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
`year`	No	Solar year, 1900 to 2100. Defaults to the solar year in progress, which changes at Li Chun rather than on 1 January.
`month`	No	Solar month, 1 to 12, where 1 begins at Li Chun in early February. This is NOT the calendar month: solar month 1 covers roughly 4 February to 5 March. Defaults to the solar month in progress.
`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.

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already signal read-only safety, so the description adds useful behavioral context: solar-month boundaries, Li Chun start, and default month-in-progress behavior. This goes beyond the schema's defaults by explaining why months do not align with calendar months.

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?

Three tight sentences front-load the core purpose and the critical solar-calendar caveat, then state defaults and use cases. Every sentence earns its place with no filler.

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 zero-required-parameter read-only tool, the description covers the conceptual return value, key date semantics, defaults, and intended use. The lack of return-value structure detail is a minor gap given there is no output schema, but it does not seriously impair tool selection or 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%, so the baseline is 3. The description reinforces the solar-month semantics relevant to year and month but does not add significant information beyond the schema's own parameter descriptions.

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?

States a specific verb and resource ('Return the monthly flying star plate') and distinguishes it from the annual overlay. The solar-month clarification prevents confusion with calendar-month tools.

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?

Gives clear intended contexts: monthly guidance features and timing work for partial-year afflictions. Explains default behavior when parameters are omitted, but does not explicitly name sibling tools or state when to prefer the annual variant.

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?