FateStar Ziwei

紫微斗数本命盘

ziwei_chart

Read-onlyIdempotent

生成紫微斗数 (Zi Wei Dou Shu / Purple Star Astrology) 完整本命盘。输入阳历或农历出生信息, 返回: 五行局/阴阳/命主身主、十二宫 (主星辅星煞星杂曜+庙旺亮度+生年四化+空宫借星+大限年龄+长生十二神)、生年四化所在宫、格局识别 (30+ 经典格局含古籍出处)、夹宫扫描、真实出生四柱 (万年历按节气)。引擎为 FateStar 自建 (102 颗星, 三合派四化, 真太阳时修正), 0 第三方排盘库。⚠️ 三合派庚干: 化科=天同 / 化忌=太阴。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`day`	Yes	出生日 (1-31)
`hour`	Yes	出生小时 0-23 (24 小时制, 非时辰地支)
`year`	Yes	出生年 (阳历; calendarType=lunar 时填农历年)
`month`	Yes	出生月 (1-12)
`gender`	Yes	性别
`minute`	No	出生分钟 (默认 0; 配合 longitude 做真太阳时精修)
`longitude`	No	出生地经度 (东经正/西经负). 传了即启用真太阳时修正
`isLeapMonth`	No	是否闰月 (仅 calendarType=lunar 有效)
`calendarType`	No	历法: solar=公历(默认) / lunar=农历	solar
`timezoneOffset`	No	时区偏移 (UTC+8=8, UTC-5=-5). 需配合 longitude

Output Schema

TableJSON Schema

Name	Required	Description	Default
`基础`	Yes
`夹宫`	Yes
`格局`	Yes
`输入`	Yes
`service`	Yes
`十二宫`	Yes
`本命四化`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedJul 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "service": {
+      "type": "string"
+    },
+    "十二宫": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "基础": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "夹宫": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "本命四化": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "格局": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "输入": {
+      "additionalProperties": true,
+      "type": "object"
+    }
+  },
+  "required": [
+    "service",
+    "输入",
+    "基础",
+    "十二宫",
+    "本命四化",
+    "格局",
+    "夹宫"
+  ],
+  "type": "object"
+}

First observedJul 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark the operation as read-only and idempotent, so the description focuses on additional behavioral context: it uses the FateStar engine with 102 stars, San He faction transformations, true solar time correction, and no third-party libraries. It also flags a special Geng-stem rule (化科=天同 / 化忌=太阴), which is a valuable caveat for correctness. No contradiction with 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?

The description is front-loaded with purpose, then uses a colon-list to enumerate return fields, followed by engine context and a warning. Every sentence contributes unique information; the length is justified by the tool's complexity and avoids redundant or promotional wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high complexity (10 parameters, rich output schema), the description is remarkably complete: it covers input calendar types, all major output categories, engine provenance, faction-specific rules, and a correctness caveat. The output schema existing means return-value detail is not required in the description, yet the description still names the main outputs.

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?

The input schema already provides 100% parameter coverage, with descriptions for all 10 parameters including enums, ranges, defaults, and dependencies (e.g., longitude enables true solar time). The description reinforces the solar/lunar and true solar time concepts but does not add meaningful per-parameter syntax or format details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb-object pair: '生成紫微斗数...完整本命盘' (generate complete natal chart), clearly identifying the tool's resource and output. It enumerates the chart components (十二宫, 四化, 格局, etc.), distinguishing it from sibling tools like ziwei_reading and ziwei_transits.

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?

The description establishes when to use the tool: when the user provides birth date/time and wants a complete natal chart, including optional lunar calendar input. However, it does not explicitly exclude transits or reading use cases or name sibling tools, so it lacks a clear when-not-to-use statement.

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

All FateStar Ziwei tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool targets a distinct aspect of Zi Wei Dou Shu: chart generation, AI-powered reading, and transit calculations. There is no overlap in purpose, and the descriptions clearly differentiate them.

Naming Consistency5/5

All tools follow a consistent 'ziwei_' prefix followed by a descriptive noun (chart, reading, transits). The naming pattern is uniform and predictable.

Tool Count4/5

Three tools is on the lower end but appropriate for a niche astrology domain. Each tool is substantial and covers a major functional area, making the set feel well-scoped rather than incomplete.

Completeness4/5

The tools cover the essential lifecycle: creating a natal chart, getting an interpretation, and calculating transits. Minor gaps exist (e.g., no dedicated compatibility or lunar date conversion tool), but core workflows are complete.

紫微斗数本命盘

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources