Skip to main content
Glama
ChesterRa

命盘 Mingpan

by ChesterRa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

八字大運列表

bazi_dayun

Calculate major luck cycles (Dayun) from birth date, time, and gender, returning 10-year periods with pillars, ages, years, direction, and starting age.

Instructions

八字大運列表。

返回命主一生的大運週期（十年一運）：

  • 大運干支

  • 起止虛歲

  • 對應公曆年份

  • 起運方向（順行/逆行）

  • 起運年齡

用於了解人生各階段的運勢大框架。

Input Schema

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

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 / count / description
      Previous value: -"Number of DaYun periods to display (default 10)"New value: +"Number of periods to display (default 10)"
    • 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

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It describes the returned fields (a form of output transparency) but does not state that the operation is read-only, non-destructive, or mention any other behavioral traits like authentication or rate limits. This is a significant gap for a tool with zero annotation coverage.

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?

The description is concise and front-loaded: it starts with the tool name, then lists the returned fields, and ends with a usage sentence. The only minor redundancy is the first sentence restating the title, but otherwise every sentence earns its place.

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?

Given the absence of an output schema, the description usefully lists the return fields (大運干支, 起止虛歲, etc.), which is essential. It also provides a usage context. However, it omits any behavioral safety information, which would be expected without annotations, leaving a small 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 description coverage is 100%, so all parameters are well documented in the input schema. The description adds no additional parameter meaning beyond what the schema provides, which is the baseline expectation when schema coverage is high.

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 states a specific verb and resource: it returns the DaYun cycles (十年一運) with listed fields. It is clear that this tool is for the major ten-year luck periods, distinguishing it implicitly from siblings like bazi_liunian (annual) or bazi_basic (basic chart), though no sibling is named explicitly.

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?

The description provides an implied usage context: '用於了解人生各階段的運勢大框架' (used to understand the overall framework of fortune in each life stage). However, it does not explicitly state when to use this tool versus alternatives like bazi_basic or bazi_liunian, leaving comparisons to inference.

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