Skip to main content
Glama

cn402_fengshui_move-day

Find lucky moving dates by entering a date range and optional birth year to avoid zodiac clashes, based on traditional Feng Shui rules.

Instructions

Lucky moving day / Feng Shui moving date selection / 搬家择日 / 入宅择吉 / Chinese moving day calculator / auspicious move-in dates / housewarming date / yi an chuang / 宜安床 / pick lucky day to move. Find auspicious days for moving house within a date range, considering the resident's birth year (zodiac clash) and traditional moving rules.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
birthYearNoHead-of-household birth year (optional, for zodiac clash check)
endYesEnd date YYYY-MM-DD (required)
startYesStart date YYYY-MM-DD (required)
Behavior3/5

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

The description mentions considering birth year and traditional moving rules, and notes a price (unknown on Base, auto-paid in USDC). However, it lacks details on what the output looks like (e.g., list of dates) and any limitations. No annotations are present, so the description carries the burden.

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 is front-loaded with synonyms in multiple languages, which may aid discoverability but adds redundancy. The price line is separate. It is not overly long but could be more structured.

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?

The description does not specify the output format (e.g., list of dates, calendar view) or any result details. Given no output schema, this is a significant gap. The price context is useful but not sufficient.

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 parameter descriptions are clear. The description adds that birthYear is for zodiac clash, but this does not significantly enhance understanding beyond the schema.

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 identifies the tool as a Feng Shui moving date selector with multiple keywords and specifics ('Find auspicious days for moving house within a date range'), which distinguishes it from sibling tools like cn402_almanac or other fengshui tools.

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?

The description implies usage for moving date selection but does not explicitly state when to use this tool versus alternatives like the generic almanac. No when-not or exclusions are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/x402node/x402-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server