Skip to main content
Glama
ChesterRa

命盘 Mingpan

by ChesterRa

八字流日列表

bazi_liuri

Generates daily BaZi fortunes for a specified month, including major luck, annual, and monthly cycles, to support precise date selection.

Instructions

八字流日列表。

返回指定月份內的每日運勢(含上下文):

  • 當前大運、流年、流月資訊

  • 公曆日期

  • 干支日

用於精細的日期選擇。

Input Schema

TableJSON 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 of the month (GanZhi string or Gregorian year)
ganzhiMonthYesThe month to query (either GanZhi string or month number 1-12)

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 of the month"New value: +"The year of the month (GanZhi string or Gregorian year)"
    • 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.7/5.0
Behavior3/5

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

未提供 annotations,描述披露會回傳大運、流年、流月、公曆日期與干支日等內容,對讀取型工具而言提供部分透明度;但未說明是否為唯讀、是否需要完整出生資料、有無副作用或限制。

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?

開頭先點明工具用途,接著用條列列出回傳上下文,最後補一句使用情境;沒有冗餘鋪陳,結構前重後輕。

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?

工具參數多(12 個、7 個必填)且無 output schema,描述雖列出部分回傳欄位,但未交代必填出生資料與 ganzhiYear/ganzhiMonth 查詢月份之間的整體輸入邏輯;靠 schema 補足,但描述本身仍有缺口。

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 描述覆蓋率 100%,參數意義已由 schema 完整承載;描述僅提到「指定月份」,未對 12 個參數(尤其出生資料 vs 查詢月份)增加額外語意。

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?

描述以具體動詞「返回」與資源「每日運勢」界定工具,並說明以指定月份為範圍;與 bazi_liunian/bazi_liuyue 的年度/月度粒度有別。但未點名任何兄弟工具,故未達 5。

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?

「用於精細的日期選擇」給出明確使用情境,但沒有說明何時不該用、或與 bazi_liuyue/calendar_convert 等替代工具的取捨。

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