Skip to main content
Glama
Sign In
命盘 Mingpan

命盘 Mingpan

by ChesterRa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

八字流月列表

bazi_liuyue

Generate a 12-month BaZi fortune list for a given year, using solar-term month boundaries. Returns Ganzhi months, solar term dates, and Gregorian ranges to help plan annual activities.

Instructions

八字流月列表。

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

  • 以節氣為邊界（立春起算）

  • 寅月（正月）從立春開始，約2月4日

  • 丑月（臘月）跨越公曆年界

返回指定年份的12個月運勢：

  • 干支月

  • 節氣起止

  • 公曆日期範圍

用於規劃年度活動時機。

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>",
      "ganzhiYear": "<ganzhiYear>"
    },
    "name": "bazi_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出生地經度（真太陽時校正，可選）
ganzhiYearYesThe year to query (either GanZhi string like '乙巳' or Gregorian year like 2025)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 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 / ganzhiYear / description
      Previous value: -"The year to query (either GanZhi string or Gregorian year)"New value: +"The year to query (either GanZhi string like '乙巳' or Gregorian year like 2025)"
    • 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

B3.4/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 burden and does add real domain behavior: solar-term months, exact boundaries (立春/寅月), and that 丑月 crosses the Gregorian year line. However it says nothing about whether natal birth data is required, permissions, rate limits, or result size, so transparency is partial.

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?

Front-loaded with the important 節氣月 caveat, then the return shape, then use case – a sound ordering. It repeats the title phrase '八字流月列表' at the start, which is minor waste, but overall it is tight.

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?

11 parameters (6 required) and no output schema, so the description's enumeration of return fields is genuinely helpful. But it leaves the critical ambiguity between year/ganzhiYear and the required birth-data inputs unresolved, which an agent needs in order to call it correctly.

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 mentions '指定年份' but does not disambiguate the two year inputs (year vs ganzhiYear) or explain how a query year relates to the required birth date fields, adding little beyond the schema.

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?

States a specific verb+resource: returns the 12 monthly fortunes for a given year, enumerating the returned fields (干支月, 節氣起止, 公曆日期範圍). It is largely distinguishable from bazi_liunian/bazi_liuri by the '12 months' scope, though it never names those siblings directly.

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?

'用於規劃年度活動時機' gives an implied use context (annual planning), but there is no explicit when-not or routing to siblings such as bazi_liunian for yearly or bazi_liuri for daily granularity. Usage is inferred rather than stated.

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