Skip to main content
Glama
Sign In
x402-mcp

x402-mcp

Official
by x402node
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cn402_fengshui_business-direction

Get auspicious business door direction and wealth corner recommendations based on owner's Kua and business type. Input gender, birth year, and optional industry.

Instructions

Business direction / shop entrance Feng Shui / 商铺方向 / store door direction / business luck direction / 财位 / wealth direction / 旺财方位 / commercial Feng Shui / where to face shop. Recommend the most auspicious door-facing direction and wealth corner for a business based on owner's kua and business type.

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": {
      "gender": "<gender>",
      "year": "<year>"
    },
    "name": "cn402_fengshui_business-direction"
  }
}

Input Schema

NameRequiredDescriptionDefault
genderYesM | F (required)
industryNoretail | restaurant | office | service (optional)
yearYesOwner birth year YYYY (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions that the tool recommends auspicious directions and wealth corners based on inputs, and it discloses a pricing model (auto-paid in USDC). However, it does not describe rate limits, data sources, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose and redundant, repeating similar phrases in multiple languages (e.g., 'shop entrance Feng Shui / 商铺方向 / store door direction / business luck direction'). It could be more concise. The essential sentence is buried in the middle.

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

Completeness2/5

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

There is no output schema, and the description does not explain what the tool returns (e.g., direction name, degrees, etc.). It lacks details about prerequisites or how the recommendation is formatted. For a tool with only 3 parameters, this is a significant gap.

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 adds context by explaining that gender and year are used to compute kua, and industry indicates business type. No additional detail beyond what the schema 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 clearly states the tool's purpose: to recommend the most auspicious door-facing direction and wealth corner for a business based on owner's kua and business type. It distinguishes itself from sibling tools like cn402_fengshui_direction and cn402_fengshui_bed-direction by focusing on commercial feng shui.

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 provides context for when to use the tool (business/shop entrance feng shui) and lists required parameters. It implies usage by mentioning 'owner's kua' (derived from gender and year) and business type. However, it does not explicitly state when not to use it or name 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