bazi_chart八字排盘 from birth date and hour: four pillars (年月日时柱), five-element counts, 纳音, zodiac. Uses true solar-term boundaries.
| Name | Required | Description | Default |
|---|---|---|---|
| datetime | Yes | Birth datetime YYYY-MM-DDTHH:mm |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds the computational detail of using true solar-term boundaries and enumerates the chart contents, which provides useful behavioral context beyond the annotations.
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?
The description is a single, information-dense sentence that front-loads the primary output and key features without redundancy.
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?
Given the tool's complexity, the one-parameter schema, clear annotations, and presence of an output schema, the description covers the essential purpose and behavior. It could mention timezone handling, but the solar-term boundary detail partially addresses temporal context. Overall, it's sufficiently complete.
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 fully describes the datetime parameter with format and meaning. The description's mention of 'birth date and hour' reinforces this but does not add new semantic details. Baseline 3 for high schema coverage is appropriate.
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?
The description clearly states the tool computes a BaZi chart from birth date/time, enumerating key outputs (four pillars, five elements, na yin, zodiac) and the solar-term boundary method. This distinguishes it from sibling tools like lunar_calendar and pick_lucky_days.
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?
The description implies the tool is for generating BaZi charts from birth date/time, but it does not explicitly state when to prefer it over sibling tools or mention exclusions. Usage context is clear but relies on inference.
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.
Each tool targets a narrow, distinct concern: bazi_chart for birth charts, cn_holiday for public holidays, huangli for daily auspicious items, lunar_calendar for lunar dates, and pick_lucky_days for selecting dates. There is no meaningful overlap; even the related huangli and pick_lucky_days are clearly separated by direction (given date vs. searching dates).
All names are lowercase snake_case, so style is consistent, but the grammatical pattern is mixed: bazi_chart and huangli are nouns, lunar_calendar is an adjective-noun, pick_lucky_days is verb-object, and what_can_you_do is a sentence. This is readable but lacks a uniform verb_noun convention.
Six tools is a well-scoped set for a Chinese almanac/calendar server. Each tool covers a distinct major feature (charts, holidays, almanac, lunar info, date selection) with no redundancy, and the count is comfortably within the ideal 3-15 range.
The server covers the core needs of its domain: lunar conversion, public holidays, daily almanac rulings, lucky date selection, and bazi charts. There are no obvious dead ends; the addition of what_can_you_do also helps agents navigate the remaining surface, making the set feel comprehensive for its intended purpose.