Skip to main content
Glama
ChesterRa

命盘 Mingpan

by ChesterRa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

紫微小限列表

ziwei_xiaoxian

Calculate Zi Wei Dou Shu minor limit (Xiaoxian) annual fortune for a birth chart, returning each year's palace, main stars, age, and four transformations across a specified age range.

Instructions

紫微小限列表。

小限是紫微斗數中的年度運限單位，每年一宮：

  • 虛歲（1歲起）

  • 對應公曆年份

  • 小限宮位（根據出生年支起宮，男順女逆）

  • 宮內主星

  • 所屬大限

  • 小限四化

小限與流年並列但計算方式不同：

  • 小限：以出生年支定起宮，逐年移宮

  • 流年：以該年地支定宮位

層級順序：大限 > 小限 > 流年 > 流月 > 流日

Input Schema

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

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

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses returned fields (虛歲, 公曆年份, 宮位, 主星, 大限, 四化) and calculation rules (出生年支起宮, 男順女逆). It omits side-effect/safety statements, but for a calculation tool this is largely inferable.

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 front-loaded, uses bullet points for returned fields, and separates the 小限 vs 流年 comparison and hierarchy clearly. Each section earns its place for a complex 12-parameter tool.

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 no output schema, the description usefully lists the fields returned and the conceptual level of 小限. It could more explicitly state the return structure and how startAge/endAge bound the output, but it is otherwise complete for this domain calculator.

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 already documents all 12 parameters. The description adds conceptual context about 小限 but no additional parameter-specific semantics or input format details.

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 names the resource (紫微小限列表) and explains what 小限 is, including returned fields. It also distinguishes conceptually from 流年 via a comparison and hierarchy. However, it lacks an explicit action verb and does not name sibling tool IDs 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides clear context for when the concept applies, contrasting 小限 with 流年 and stating the hierarchy 大限 > 小限 > 流年 > 流月 > 流日. It does not give explicit when-not guidance or name alternative sibling tools directly.

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