Get lunar vegetarian days for a given solar date and calendar type
| Name | Required | Description | Default |
|---|---|---|---|
| solar_day | No | Day, omit if you want to get veggie days for the whole month | |
| solar_year | Yes | Solar Year in YYYY format (e.g. 2026) | |
| solar_month | Yes | Solar Month, valid values are 1-12 | |
| lunar_vegetarian_calendar_type | No | Lunar vegetarian calendar type, one of: two_days, four_days, six_days, eight_days, ten_days, default is ten_days |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention whether the operation is read-only, potential side effects, error conditions, or the format of the returned data. The word 'Get' hints at a non-mutating lookup, but this is not explicit, and no further behavioral context is given.
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, front-loaded sentence that states the action and resource with no extraneous words. It is appropriately concise for a tool of this simplicity and earns every word.
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?
The tool has 4 parameters and no output schema, but the description provides only a minimal statement. It does not explain what 'lunar vegetarian days' are, how the optional day affects results, what the return value looks like, or any edge cases. This is insufficient for an agent to correctly use the tool, especially given the lack of output 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 input schema fully describes all 4 parameters with 100% coverage, so the baseline is 3. The description adds the high-level summary of 'solar date' and 'calendar type', but it does not introduce any new meaning beyond what the schema already provides, nor does it clarify the optional solar_day parameter's behavior.
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 action ('Get') and the resource ('lunar vegetarian days'), which is a specific and distinct functionality compared to sibling tools like date conversion or canchi. However, it does not explicitly differentiate itself from get_lunar_days_for_month, so it falls short of a full 5.
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 gives context by specifying inputs ('for a given solar date and calendar type') but does not explicitly state when to use this tool over alternatives or include any exclusions. Usage is implied rather than directly guided.
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 has a clearly distinct purpose: converting between lunar and solar dates, getting Can Chi, retrieving lunar days for a month, and obtaining vegetarian days. There is no overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case, such as 'convert_date_lunar2solar' and 'get_canchi'. The naming is predictable and uniform.
With 5 tools, the server is well-scoped for its purpose of Vietnamese calendar conversions and queries. Each tool serves a necessary function without being excessive or insufficient.
The tool set covers core functionalities: bidirectional date conversion, Can Chi, lunar days per month, and vegetarian days. Minor omissions like holiday lookup or more detailed lunar year queries are acceptable for a focused server.
