Skip to main content
Glama

calendar-mcp

Solar To Lunar

solar_to_lunar

将公历日期转换为农历日期,返回农历年月日、是否闰月、生肖、干支等信息

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": "<year>",
      "month": "<month>",
      "day": "<day>"
    },
    "name": "solar_to_lunar"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYes公历日,如 17
yearYes公历年,如 2026
monthYes公历月,如 2

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / day / description
      Added value: +"公历日,如 17"
    • removedInput schema / properties / day / title
      Removed value: -"Day"
    • addedInput schema / properties / month / description
      Added value: +"公历月,如 2"
    • removedInput schema / properties / month / title
      Removed value: -"Month"
    • addedInput schema / properties / year / description
      Added value: +"公历年,如 2026"
    • removedInput schema / properties / year / title
      Removed value: -"Year"
    • removedInput schema / title
      Removed value: -"solar_to_lunarArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose the returned fields (leap month, zodiac, ganzhi), which tells the agent the conversion is calendrically rich rather than a bare date swap. However, it says nothing about supported year ranges, out-of-range input behavior, or error handling — meaningful gaps for a computation with no safety annotations.

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?

A single front-loaded sentence that states the conversion and then enumerates the outputs, with no filler. The output enumeration is somewhat redundant given a dedicated output schema exists, which keeps it just below top marks.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-required-integer pure function with a full output schema, the description covers what the tool does and what it yields. The only real omission is the supported Gregorian year range, which matters for a lunar-calendar conversion but is a narrow gap.

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 each of the three integer parameters already carries an inline example ('公历日,如 17'), so the schema does the heavy lifting. The description adds no format, range, or validation meaning beyond what is already structured, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('将公历日期转换为农历日期') and makes the conversion direction unambiguous, which is the key distinction an agent needs. It stops short of any explicit contrast with the holiday-query siblings, but the purpose itself is concrete and unmistakable.

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?

Usage is only implied: an agent can infer this is the tool for date-system conversion, but the description states no when-to-use conditions, no preconditions, and no alternatives. For a single-purpose conversion utility this is acceptable but leaves the agent to reason from the name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.