Skip to main content
Glama
Sign In
命盘 Mingpan

命盘 Mingpan

by ChesterRa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

農曆公曆互轉

calendar_convert

Convert between lunar and solar dates with leap month support, returning authoritative calendar data, Ganzhi year/month/day, and zodiac signs. Use it to avoid AI's incorrect leap month guesses.

Instructions

農曆與公曆日期互轉（含閏月處理、干支年月日、生肖）。

農曆閏月分配無簡單規律（哪年閏幾月由天文計算決定），AI 經常猜錯。 本工具返回權威曆表數據。

支持兩個方向：

  • solar → lunar：輸入公曆日期，返回農曆日期（含是否閏月）

  • lunar → solar：輸入農曆日期（isLeapMonth 標記閏月），返回公曆日期

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": {
      "direction": "<direction>",
      "year": "<year>",
      "month": "<month>",
      "day": "<day>"
    },
    "name": "calendar_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYes日期
yearYes年份
monthYes月份（1-12）
directionYes轉換方向
isLeapMonthNo農曆輸入時是否為閏月（lunar2solar 方向）

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.8

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that leap-month allocation is astronomically determined and that outputs are authoritative, which is genuinely useful, but says nothing about error handling for out-of-range dates, return shape, or performance. Adequate but incomplete for a zero-annotation tool.

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

Conciseness5/5

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

Front-loads the purpose, then the rationale, then the two directions as a compact bulleted list. Every sentence earns its place with no redundancy.

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?

With no output schema and no annotations, the description needs to stand alone, and it does cover both directions, leap-month input marking, and the returned components (lunar date, ganzhi, zodiac). It omits error/range behavior for invalid combos, keeping it just short of fully self-contained.

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 description coverage is 100%, so the baseline is 3. The description reinforces that direction selects the input interpretation and that isLeapMonth marks a leap month only on the lunar→solar path, adding modest meaning, but introduces no new format or constraint detail beyond the schema.

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?

States a specific verb+resource ('農曆與公曆日期互轉') and enumerates scope beyond the name: 閏月處理, 干支年月日, 生肖. An agent can distinguish this from siblings like jieqi_query or the bazi_* family without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear reason to use it (AI commonly mis-guesses leap-month assignment, this returns authoritative data) and spells out the two supported directions. It does not explicitly name which sibling to prefer when, so it stops short of 5, but the usage context is well established.

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

Deploy Server

Other Tools