pick_lucky_daysFind auspicious days in a month for an event: 结婚/领证/搬家/开业/装修/出行/签约/订婚/安床/安葬 or any 黄历宜 term.
| Name | Required | Description | Default |
|---|---|---|---|
| event | Yes | Event keyword in Chinese, e.g. 搬家 | |
| month | No | YYYY-MM, default current month |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent safety. The description adds context about accepted event terms but does not disclose output format or dependency on the Chinese almanac beyond the '黄历宜' reference.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single, focused sentence with no redundancy. Front-loaded with the primary function and scoped by month.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
A simple tool with 2 params, good annotations, and an output schema. The description covers the purpose and parameter flexibility, though it does not mention behavior for invalid events or the default month (already in schema).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes both parameters (100% coverage). The description enriches semantics by listing concrete examples and stating 'any 黄历宜 term' accepts broader input than the schema's generic 'Event keyword in Chinese'.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the action ('Find'), target ('auspicious days'), and context ('in a month for an event'). The list of example events and 'any 黄历宜 term' broaden understanding while distinguishing it from generic calendar tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides implied usage via specific event types but does not explicitly contrast with sibling tools like 'huangli' or state when not to use. No alternatives are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly distinct: bazi_chart, lunar_calendar, huangli, pick_lucky_days all relate to Chinese calendrical/astrological concepts but have different purposes (birth chart, lunar info, almanac, lucky day selection). However, bazi_chart and lunar_calendar both touch on 干支/zodiac; pick_lucky_days could overlap with huangli. Minor ambiguity, but descriptions clarify.
Tool names are all snake_case and mostly descriptive, but they don't follow a strong verb_noun pattern (e.g., pick_lucky_days is verb+noun, but bazi_chart and phone_info are noun-like). Slight inconsistency in style, but the pattern is predictable enough.
10 tools is well-scoped for a China-focused utility server. Each tool serves a distinct purpose (ID validation, phone info, holidays, calendar, pinyin, network reachability), and the count feels reasonable without being bloated or thin.
The server covers a broad range of China-specific utilities, but there are gaps: no tool for Chinese address parsing, no tool for bank card validation, no tool for translation. While the existing set covers common needs, the 'china' theme could benefit from more coverage. Also, what_can_you_do suggests recipes but the actual tool set lacks some common use cases.