Skip to main content
Glama
Sign In
x402-mcp

x402-mcp

Official
by x402node
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cn402_fengshui_feixing

Calculate Xuan Kong Flying Stars chart for a given year and house sitting direction. Returns 9-grid star map for Feng Shui analysis.

Instructions

Flying Stars / 玄空飞星 / Xuan Kong Fei Xing / period 9 flying stars / 三元九运 / Feng Shui period 1-9 / 9-grid star chart / annual monthly flying stars / Chinese space-time Feng Shui. Compute the Flying Stars (9-grid) chart for a given year and house orientation (sitting direction).

Price: unknown on Base (auto-paid in USDC).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sitting": "<sitting>",
      "year": "<year>"
    },
    "name": "cn402_fengshui_feixing"
  }
}

Input Schema

NameRequiredDescriptionDefault
sittingYesHouse sitting direction (e.g. 子, 北 - required)
yearYesYear YYYY (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided. The description only mentions 'Compute' which implies a non-destructive operation but does not confirm read-only behavior, authentication needs, or payment implications. The pricing note is unclear and does not clarify behavioral traits.

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 concise with a single clear sentence after a list of keywords. It is front-loaded but includes redundant synonyms that could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple two-parameter schema, the description is mostly adequate but lacks details on the output format or what the 'chart' contains. No output schema exists, so more context on return value would help.

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 coverage is 100%, so baseline is 3. The description mentions 'year and house orientation' but adds no additional meaning beyond what the parameter descriptions already provide.

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 explicitly states it computes a Flying Stars chart for a given year and sitting direction, using multiple keywords for clarity. It distinguishes itself from sibling fengshui tools by focusing on the 9-grid star chart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus other fengshui tools. The description implies usage for computing flying stars but lacks exclusions or mentions of alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools