Skip to main content
Glama
Sign In
命盘 Mingpan

命盘 Mingpan

by ChesterRa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

紫微流月列表

ziwei_liuyue

Generate Ziwei astrology monthly forecasts based on lunar months. Retrieve monthly palace positions, stars, and four transformations to plan annual activities.

Instructions

紫微流月列表。

重要：紫微流月使用【農曆月】，非節氣月！

  • 以農曆初一為邊界

  • 正月從春節開始

  • 閏月單獨顯示（如"閏六月"）

返回指定年份的流月運勢（含上下文）：

  • 當前大限、小限、流年資訊

  • 農曆月份及公曆日期範圍

  • 流月宮位及宮內主星

  • 完整四化系統（本命/大限/小限/流年/流月）

用於規劃年度活動時機。

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>",
      "hour": "<hour>",
      "gender": "<gender>",
      "lunarYear": "<lunarYear>"
    },
    "name": "ziwei_liuyue"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYes日 1-31
hourYes時 0-23
nameNo命主姓名（可選）
yearYes公曆年 1900-2100
monthYes月 1-12
genderYes性別（影響大運順逆）
minuteNo分 0-59，默認 0
isLunarNo輸入日期是否為農曆，默認公曆
timezoneNoIANA 時區名（如 America/New_York）。默認北京時間；設置後輸入時間按此時區換算為北京時間排盤。農曆輸入時忽略
longitudeNo出生地經度（真太陽時校正，可選）
lunarYearYesThe lunar year (Gregorian year) to query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv0.1.8
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / day / description
      Previous value: -"Birth day (1-31)"New value: +"日 1-31"
    • changedInput schema / properties / gender / description
      Previous value: -"Gender for fortune direction calculation"New value: +"性別（影響大運順逆）"
    • changedInput schema / properties / hour / description
      Previous value: -"Birth hour in 24-hour format (0-23)"New value: +"時 0-23"
    • changedInput schema / properties / isLunar / description
      Previous value: -"Whether the input date is in lunar calendar (農曆). If true, will be converted to solar calendar internally."New value: +"輸入日期是否為農曆，默認公曆"
    • changedInput schema / properties / longitude / description
      Previous value: -"Birth location longitude for true solar time adjustment"New value: +"出生地經度（真太陽時校正，可選）"
    • changedInput schema / properties / minute / description
      Previous value: -"Birth minute (0-59)"New value: +"分 0-59，默認 0"
    • changedInput schema / properties / month / description
      Previous value: -"Birth month (1-12)"New value: +"月 1-12"
    • changedInput schema / properties / name / description
      Previous value: -"Subject name (optional)"New value: +"命主姓名（可選）"
    • addedInput schema / properties / timezone
      Added value: +{
+  "description": "IANA 時區名（如 America/New_York）。默認北京時間；設置後輸入時間按此時區換算為北京時間排盤。農曆輸入時忽略",
+  "type": "string"
+}
    • changedInput schema / properties / year / description
      Previous value: -"Birth year (e.g., 1990)"New value: +"公曆年 1900-2100"
  2. First observedv0.1.3

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description bears the full burden. It discloses a critical behavioral rule about using lunar months (not solar terms) with detailed boundary logic, and enumerates the returned data. However, it does not state whether the operation is read-only or mention any side effects, leaving some behavioral gaps.

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?

The description is well-structured with front-loaded purpose, a prominent important note, and clear bullet points. Every sentence contributes useful information without 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, the description sufficiently explains the return contents (context info, lunar months, palaces, four transformations). It covers the essential complexity for an 11-parameter tool, though it omits details like return format or error handling.

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 schema fully documents all parameters. The description only adds that the year specifies the query target ('指定年份'), which is marginal beyond what the schema already provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states it returns monthly fortune for a specified year, with a specific verb-resource combination ('返回指定年份的流月運勢'). It distinguishes itself from siblings by emphasizing '流月' (monthly) and detailing output content, though it does not explicitly name alternatives like ziwei_liunian.

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?

It provides a when-to-use hint ('用於規劃年度活動時機') but lacks explicit guidance on when to choose this over monthly or annual alternatives, and no exclusions are stated. The usage context is implied rather than fully specified.

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