Skip to main content
Glama
Sign In
x402-mcp

x402-mcp

Official
by x402node
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cn402_fengshui_bagua-direction

Map the eight trigrams to compass directions using Pre-Heaven and Post-Heaven schemes. Retrieve direction mappings for Qian, Kun, Zhen, Xun, Kan, Li, Gen, Dui for feng shui analysis.

Instructions

Bagua direction mapping / 八卦方位 / Eight Trigrams compass / Pre-Heaven Post-Heaven Bagua direction / 先天后天八卦方位 / Qian Kun Zhen Xun Kan Li Gen Dui / Heaven Earth Thunder Wind Water Fire Mountain Lake direction. Get direction mapping for each of the 8 trigrams in both Pre-Heaven and Post-Heaven schemes.

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
schemeNopreHeaven | postHeaven (optional, default both)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description must convey behavioral traits. It fails to indicate that the tool is read-only, idempotent, or any constraints like rate limits or required permissions. The price note is not a behavioral trait.

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

Conciseness3/5

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

The description includes a long list of synonyms that clutter the start and a price note irrelevant to functionality. The core instruction is concise, but the extra verbiage reduces efficiency. It is adequately but not optimally concise.

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 no output schema, the description should hint at what the tool returns; it does not specify the output format. The price mention is tangential. The basic purpose and parameter are covered, but completeness is average.

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%, and the schema description already specifies the parameter 'scheme' with allowed values and default. The description adds minimal extra meaning; synonyms are not directly parameter-related. Baseline 3 applies.

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 action: 'Get direction mapping for each of the 8 trigrams in both Pre-Heaven and Post-Heaven schemes.' It uses specific verbs and resources, differentiating it from sibling fengshui tools that focus on other aspects like bed or business directions.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It lacks context such as prerequisites or comparisons with sibling tools like cn402_fengshui_direction, leaving the agent without decision support.

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