Skip to main content
Glama

lunardate

Convert a Gregorian date to the traditional Chinese lunar calendar, returning the lunar year with zodiac and lunar date in Chinese characters.

Instructions

Gregorian-Lunar Calendar Conversion API Request

Parameters:

  • date: Gregorian date to convert (YYYY-MM-DD format)

Request Example: https://data.weather.gov.hk/weatherAPI/opendata/lunardate.php?date=2025-07-26

Response Keys:

  • LunarYear: Lunar year in traditional Chinese with zodiac (e.g. "癸卯年,兔")

  • LunarDate: Lunar date in traditional Chinese (e.g. "六月初二")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesGregorian date to convert (YYYY-MM-DD format)
Behavior3/5

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

No annotations present. Description covers input format and response keys but lacks details on rate limits, error handling, or supported date range. Adequate for basic understanding but not comprehensive.

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

Conciseness4/5

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

Concise and well-structured: purpose, parameter, example, response keys. Every line adds value. Could be slightly more organized but very efficient.

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?

No output schema, but description lists response keys. However, lacks context on date range validity, timezone, or API restrictions. Reasonably complete for a simple conversion tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds value with usage example and response key explanation. Exceeds baseline by providing concrete illustration of how the parameter is used.

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?

Description clearly states the tool performs Gregorian-Lunar calendar conversion. Provides example and response keys, making purpose unmistakable. Distinct from all sibling weather 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?

No explicit guidance on when to use or alternatives. However, siblings are all weather-related, so implicit differentiation. Could be improved with a note on date range or timezone relevance.

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/louiscklaw/mcp-hko'

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