Skip to main content
Glama
ChesterRa

命盘 Mingpan

by ChesterRa

ziwei_liuyue

Retrieve yearly flow month forecasts for planning annual activities. Calculates monthly star positions and transformations based on birth data and target lunar year.

Instructions

紫微流月列表。

重要:紫微流月使用【农历月】,非节气月!

  • 以农历初一为边界

  • 正月从春节开始

  • 闰月单独显示(如"闰六月")

返回指定年份的流月运势(含上下文):

  • 当前大限、小限、流年资讯

  • 农历月份及公历日期范围

  • 流月宫位及宫内主星

  • 完整四化系统(本命/大限/小限/流年/流月)

用于规划年度活动时机。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYesBirth year (e.g., 1990)
monthYesBirth month (1-12)
dayYesBirth day (1-31)
hourYesBirth hour in 24-hour format (0-23)
minuteNoBirth minute (0-59)
genderYesGender for fortune direction calculation
longitudeNoBirth location longitude for true solar time adjustment
isLunarNoWhether the input date is in lunar calendar (農曆). If true, will be converted to solar calendar internally.
nameNoSubject name (optional)
lunarYearYesThe lunar year (Gregorian year) to query
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: uses lunar months, returns specific items like current year, month, and fortune details. However, it does not mention permissions, rate limits, or side effects.

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 fairly concise and organized with bullet points, front-loading the key point about lunar months. Minor redundancy could be trimmed, but overall good.

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 the complexity (10 params, no output schema), the description provides a good overview of what the tool does and returns. It could explain some parameters like longitude and the output format more, but it's adequate.

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%, so baseline is 3. The description does not add significant meaning beyond the schema; it focuses on output rather than parameter details.

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 clearly states the tool returns '流月运势' (monthly fortunes) for a given year, using lunar months. It distinguishes from sibling tools by specifying it's about monthly fortunes, while siblings cover basic, day, hour, etc.

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 mentions '用于规划年度活动时机' (used for planning annual activity timing) and emphasizes using lunar months. However, it does not explicitly state when to use this tool versus alternatives or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ChesterRa/mingpan'

If you have feedback or need assistance with the MCP directory API, please join our Discord server