Skip to main content
Glama
ChesterRa

命盘 Mingpan

by ChesterRa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

紫微基礎排盤

ziwei_basic

Compute a basic Zi Wei Dou Shu chart from birth date and time, returning palace positions, star placements, and four transformations in structured text for AI analysis.

Instructions

計算紫微斗數命盤（基礎排盤）。

輸入出生時間，返回完整的紫微命盤信息：

  • 十二宮位排布及干支

  • 各宮主星及亮度（廟/旺/得/利/平/不/陷）

  • 各宮輔星配置

  • 命宮與身宮位置

  • 五行局、命主、身主

  • 本命四化（化祿/權/科/忌）

時區說明：默認按北京時間排盤；海外出生者請提供 timezone 參數。

輸出為結構化文本，便於 AI 分析解讀。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayYes日 1-31
hourYes時 0-23
nameNo命主姓名（可選）
yearYes公曆年 1900-2100
monthYes月 1-12
detailNoOutput detail levelstandard
genderYes性別（影響大運順逆）
minuteNo分 0-59，默認 0
isLunarNo輸入日期是否為農曆，默認公曆
timezoneNoIANA 時區名（如 America/New_York）。默認北京時間；設置後輸入時間按此時區換算為北京時間排盤。農曆輸入時忽略
longitudeNo出生地經度（真太陽時校正，可選）
targetYearNoCalculate yearly fortune for this specific year
includeDecadesNoInclude decade fortune (大限)
includeMutagenNoInclude four mutagens (四化)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 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 (required for ZiWei 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: +"輸入日期是否為農曆，默認公曆"
    • addedInput schema / properties / longitude
      Added value: +{
+  "description": "出生地經度（真太陽時校正，可選）",
+  "maximum": 180,
+  "minimum": -180,
+  "type": "number"
+}
    • 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"
    • addedInput schema / properties / name
      Added value: +{
+  "description": "命主姓名（可選）",
+  "type": "string"
+}
    • addedInput schema / properties / targetYear / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / targetYear / minimum
      Added value: +-9007199254740991
    • 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?

With no annotations, the description carries full burden and covers the two behaviors that matter for a computation tool: timezone handling (defaults to Beijing time, overridden by the timezone param) and output form (structured text for AI interpretation). It omits any note about the advanced params (targetYear/includeDecades/includeMutagen) that the schema exposes, so it is strong but not exhaustive.

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?

Purpose is front-loaded, followed by a scannable bulleted output inventory, then the timezone caveat and output format note. Every element earns its place; the only minor cost is the header/consumption note at the end that slightly delays the key timezone rule.

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?

For a 14-param tool with no output schema and no annotations, the description compensates by enumerating the return payload (palaces, stars, brightness, life/body palaces, five-element bureau, four transformations) and the timezone rule. The advanced parameters (targetYear, includeDecades, includeMutagen) are left unexplained, which is a modest 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 the schema already documents all 14 parameters (including the timezone and gender semantics). The description restates the timezone rule but adds no syntax or meaning beyond what the schema provides; baseline 3 is appropriate.

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 (計算/calculate) and resource (紫微斗數命盤) with the scope qualifier 基礎排盤, then enumerates the returned chart components. This clearly distinguishes it from the ziwei_daxian/liunian/liuyue siblings by implication of 'basic natal chart', though it never names an alternative 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?

Conveys the trigger condition (input birth time to get a natal chart) and one important usage rule – provide timezone for overseas births. However it offers no when-not-to-use guidance and does not route the agent to ziwei_daxian/liunian for advanced or time-based analysis, so usage is only implied.

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