FateStar Ziwei

郑大钱 AI 解读 (付费, 耗积分)

ziwei_reading

调 FateStar「郑大钱」AI 命理师 —— 知识引擎 + 郑大钱人格深度解读命盘、回答命理问题 (感情/事业/财运/健康等)。解读会结合 FateStar 知识引擎与古籍检索上下文；排盘事实仍由确定性工具提供。【调用条件】仅在用户明确选择托管解读并确认可能扣积分后调用。普通命理问题默认先用免费排盘数据。⚠️ 付费: 按问题长度/模式扣积分 (短问免费), 需 FSFSKey 开发者 Key。【没 Key】引导用户去 https://www.fatestar.top 注册免费会员 → 做新手任务领积分 → 开发者中心拿 FSFSKey Key → 配进 MCP (环境变量 FATESTAR_API_KEY 或 apiKey 参数)。【积分用完 (402)】告知用户「已切回你自己的 LLM 解读, 请去 fatestar.top 充值或等北京时间 21:00 免费重置」, 然后改用 ziwei_chart 拿命盘数据 + 你自己解读。

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)
`apiKey`	No	FSFSKey 开发者 Key (也可由 MCP server 环境变量 FATESTAR_API_KEY 提供; 旧 fs_live_ 仍兼容)
`gender`	Yes	性别
`minute`	No	出生分钟 (默认 0; 配合 longitude 做真太阳时精修)
`question`	Yes	要问郑大钱的问题 (如「今年事业运如何」「该不该换工作」)
`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
`提示`	No
`运限`	No
`需注册`	No
`需积分`	No
`剩余积分`	No
`扣除积分`	No
`现有积分`	No
`积分不足`	No
`郑大钱解读`	No

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": {
+    "剩余积分": {
+      "type": "number"
+    },
+    "扣除积分": {
+      "type": "number"
+    },
+    "提示": {
+      "type": "string"
+    },
+    "现有积分": {
+      "type": "number"
+    },
+    "积分不足": {
+      "type": "boolean"
+    },
+    "运限": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "郑大钱解读": {
+      "type": "string"
+    },
+    "需注册": {
+      "type": "boolean"
+    },
+    "需积分": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedJul 31, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond annotations, the description discloses paid nature, credit consumption based on question length/mode, requirement for FSFSKey, fallback behavior on 402, and that interpretation merges knowledge engine with ancient texts while chart facts are deterministic. No contradictions 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is longer than average but well-structured with clear sections: core purpose, call condition, payment/key warning, no-key guidance, and 402 fallback. Every sentence provides operational value, though it could be tightened slightly (e.g., key setup duplicated in multiple places).

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 tool's complexity (paid, key-dependent, fallback behavior, sibling tools), the description is comprehensive. It covers when to use, payment mechanics, key acquisition, error handling, and relationship to ziwei_chart. The presence of an output schema means return-value details are not required.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds meaningful context beyond the schema: explains the apiKey can come from environment variable, ties credit cost to question length (short questions free), and clarifies the hour is 24-hour, not earthly-branch. This adds value over the schema alone.

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 explicitly states the tool calls FateStar's Zheng Daqian AI astrologer to interpret natal charts and answer life questions (love/career/wealth/health). It clearly distinguishes itself from deterministic chart tools (ziwei_chart, ziwei_transits) by noting it provides AI-powered interpretation while chart facts come from deterministic tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description gives explicit conditional usage: only call when the user explicitly opts into hosted interpretation and confirms possible point deduction. It also states that ordinary questions should default to free chart data, and provides a clear fallback to ziwei_chart + own interpretation when no key is available or when points run out (402).

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.

郑大钱 AI 解读 (付费, 耗积分)

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources