Feng Shui MCP Server by RoxyAPI

List the nine flying stars - Xuan Kong star reference API

get_feng_shui_flying_stars

Read-only

The reference catalogue of the nine flying stars: name, Chinese characters, five phase, home palace and trigram, the period each rules, what each means, and which element strengthens or drains it. The remedy element is what the star itself produces, because a harmful star is drained by giving it somewhere to go rather than fought with the phase that controls it. A pure reference endpoint that needs no chart.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_feng_shui_flying_stars"
  }
}

Input 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
`limit`	No	Maximum items to return per page. Range: 1-9, default 9.
`offset`	No	Number of items to skip for pagination. Default 0.
`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.

Output Schema

Name	Required	Description	Default
`limit`	Yes
`stars`	Yes
`total`	Yes
`offset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026
- addedInput schema / properties / offset / default
```
Added value: +0
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
Changed3 schema fields changedSep 20, 2026
- removedInput schema / properties / offset / default
```
Removed value: -0
```
- removedInput schema / properties / offset / minimum
```
Removed value: -0
```
- changedInput schema / properties / offset / type
```
Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"
```

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "limit": {
+      "type": "number"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "stars": {
+      "items": {
+        "properties": {
+          "base": {
+            "type": "number"
+          },
+          "chinese": {
+            "type": "string"
+          },
+          "element": {
+            "type": "string"
+          },
+          "enhancer": {
+            "type": "string"
+          },
+          "keywords": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "meaning": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "nameLocalized": {
+            "type": "string"
+          },
+          "nature": {
+            "type": "string"
+          },
+          "number": {
+            "type": "number"
+          },
+          "palace": {
+            "type": "string"
+          },
+          "period": {
+            "type": "number"
+          },
+          "pinyin": {
+            "type": "string"
+          },
+          "remedy": {
+            "type": "string"
+          },
+          "trigram": {
+            "properties": {
+              "chinese": {
+                "type": "string"
+              },
+              "english": {
+                "type": "string"
+              },
+              "number": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "number",
+              "english",
+              "chinese"
+            ],
+            "type": "object"
+          }
+        },
+        "required": [
+          "number",
+          "name",
+          "chinese",
+          "pinyin",
+          "element",
+          "nature",
+          "keywords",
+          "meaning",
+          "enhancer",
+          "remedy",
+          "palace",
+          "period",
+          "base"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "limit",
+    "offset",
+    "stars"
+  ],
+  "type": "object"
+}

Changed4 schema fields changedSep 5, 2026

changedInput schema / properties / limit / default
```
Previous value: -20New value: +9
```

changedInput schema / properties / limit / description

Previous value: -"Maximum stars to return per page. Range 1 to 9, default 20."New value: +"Maximum items to return per page. Range: 1-9, default 9."

changedInput schema / properties / limit / example
```
Previous value: -20New value: +9
```

changedInput schema / properties / offset / description

Previous value: -"Number of stars to skip for pagination. Default 0."New value: +"Number of items to skip for pagination. Default 0."

First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful context by emphasizing this is a pure, static reference and explaining the remedy-element reasoning, but it does not disclose other behavioral details such as pagination behavior or response shape beyond what annotations and schema already provide.

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 dense, purposeful sentences with no filler. The description front-loads the core reference catalogue content, then adds the remedy-element nuance, and ends with the distinguishing 'needs no chart' guidance. Every sentence earns its place.

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?

For a static read-only reference endpoint, the description is complete: it states what the data is, what fields are included, the domain logic behind remedy elements, and the key distinction from chart-based tools. Output schema exists and annotations cover safety, so nothing critical is missing for an agent to call it 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?

Schema description coverage is 100%, so lang, limit, offset, and compact are already fully documented. The description adds no additional parameter-level information, which is acceptable given the schema does the heavy lifting; baseline 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 exactly what the endpoint is: a reference catalogue of the nine flying stars, listing the specific attributes returned (name, Chinese characters, five phase, home palace, trigram, ruling period, meaning, strengthen/drain elements). It also distinguishes itself from chart-based siblings by saying it is 'a pure reference endpoint that needs no chart.'

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 to use it: when you need the static reference catalogue of nine stars rather than a chart-based reading. It does not explicitly name alternatives like the annual or monthly flying star endpoints, but the 'needs no chart' phrasing makes the intended use reasonably 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 tools Inspect

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

Need Help?