Skip to main content
Glama
ChesterRa

命盘 Mingpan

by ChesterRa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

紫微流日列表

ziwei_liuri

Compute daily Zi Wei Dou Shu fortunes for every day in a given lunar month, with major, annual, monthly, and four-transformation context for precise date selection.

Instructions

紫微流日列表。

返回指定農曆月內的每日運勢（含上下文）：

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

  • 農曆日期與公曆日期對照

  • 干支日及流日宮位

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

閏月使用負數表示（如 -6 表示閏六月）。

用於精細的日期選擇。

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出生地經度（真太陽時校正，可選）
lunarYearYesThe lunar year (Gregorian year)
lunarMonthYesLunar month (1-12, use negative for leap month, e.g. -6 for leap 6th month)

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.7/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden; it discloses in detail what the return contains (multi-layer context and the complete 四化 system) and explains the negative-number leap-month convention. It does not state read-only nature or failure/edge behavior, but for a deterministic fortune calculation it is fairly transparent.

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 tool name, followed by a clean bulleted output inventory and a short note on leap months and use case. Well organized with little waste, though the summary line is slightly under-informative.

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 12 parameters, no output schema, and no annotations, the description does the necessary work by enumerating the returned fields and the leap-month encoding. Minor ambiguity remains about whether a specific 'day' input is required to scope the month's list, but overall an agent has enough to invoke it.

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 coverage is 100% and all 12 parameters are documented, so the baseline is 3. The description's note that leap months use negative numbers (e.g. -6) restates what lunarMonth already documents in the schema, adding no new semantics.

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 ('紫微流日列表', returns 每日運勢 within a lunar month) and enumerates exactly what it computes (大限/流年/流月 context, lunar↔Gregorian mapping, 干支日及宮位, full 四化 system). This clearly separates it from ziwei_liunian/liuyue/daxian siblings by its daily granularity, 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?

'用於精細的日期選擇' gives only a one-line intent with no explicit when-not-to-use or alternative tool (e.g. ziwei_liuri vs bazi_liuri). Usage is implied but left 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