Skip to main content
Glama

Feng Shui MCP Server by RoxyAPI

by com.roxyapi
OverviewDiscussionsAdmin

Annual flying stars - Yearly feng shui star chart API

get_feng_shui_flying_stars_annual_year
Read-only

Return the annual flying star plate for a solar year: which of the nine stars occupies each of the nine palaces, what it means there, and which element strengthens or drains it. The annual plate is universal and does not depend on any building, so it is the layer every yearly feng shui guide is built on. The changeover is Li Chun in early February rather than Lunar New Year, and the exact date is returned so a caller can apply the plate on the right day.

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
yearYesSolar year, 1900 to 2100. The year runs from Li Chun to Li Chun, so a date in January belongs to the previous year here.
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYes
palacesYes
centerStarYes
changeoverDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "centerStar": {
+      "type": "number"
+    },
+    "changeoverDate": {
+      "type": "string"
+    },
+    "palaces": {
+      "items": {
+        "properties": {
+          "element": {
+            "type": "string"
+          },
+          "enhancer": {
+            "type": "string"
+          },
+          "meaning": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "nameLocalized": {
+            "type": "string"
+          },
+          "nature": {
+            "type": "string"
+          },
+          "palace": {
+            "type": "string"
+          },
+          "remedy": {
+            "type": "string"
+          },
+          "star": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "palace",
+          "star",
+          "name",
+          "element",
+          "nature",
+          "enhancer",
+          "remedy",
+          "meaning"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "year": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "year",
+    "centerStar",
+    "changeoverDate",
+    "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, so safety is covered. The description adds useful behavioral context: the plate is universal, the changeover occurs at Li Chun rather than Lunar New Year, and the exact date is returned so callers apply the plate correctly.

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 sentences with no filler, front-loading the core action and output contents first. Every sentence earns its place: what it returns, how it differs from building-specific charts, and the critical date nuance.

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 output schema exists, annotations cover safety, and all parameters are fully described in the schema, the description supplies the missing domain context: the plate's universality, its role in yearly guides, and the Li Chun boundary. Nothing an agent needs to call it correctly is missing.

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 fully documents year, lang, and compact. The description reinforces the meaning of 'solar year' and the Li Chun boundary, but it does not add material information 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: 'Return the annual flying star plate for a solar year,' then enumerates what the plate contains (stars, palaces, meanings, elements). It distinguishes itself from building-dependent or monthly variants by stating the annual plate is universal and does not depend on any building.

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 clearly positions this tool as the building-independent yearly layer on which annual feng shui guides are built, giving strong context for when to use it. It does not explicitly name sibling alternatives or state when not to use it, but the universality and annual scope make the usage context clear.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources