Skip to main content
Glama
Ancient Echoes MCP

Ancient Echoes MCP

Classical Lu Ming Chart

bazi.calculate_luming
Read-only

Calculate traditional Lu Ming year-pillar Three Origins and Na Yin positions from an explicit birth time; return year stem as Lu, year branch as Ming, and Na Yin as Shen with supporting evidence.

Instructions

按完整显式出生民用时刻计算古法禄命年柱三元与纳音生旺落位,返回年干为禄、年支为命、年柱纳音为身,以及四柱、胎元、命宫、身宫的证据;不生成紫微十二人生宫、吉凶计数、总体评级或事件预测。

Input Schema

NameRequiredDescriptionDefault
dayYes
hourYes
yearYes
monthYes
minuteYes
is_maleYes
latitudeNo
apply_dstYes按 IANA 历史规则把夏令钟表时手工回拨为标准时;请求与实际应用分别留痕
city_nameNo
longitudeNo
timezone_idNo
birth_countryNo
calendar_typeYes
is_leap_monthYes
split_zi_hourYes
use_true_timeYes
birth_place_typeNo
timezone_offset_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint already establishes a safe read, and the description adds useful output-scope disclosure: it returns evidence for 四柱, 胎元, 命宫, and 身宫, and explicitly excludes other outputs. It does not, however, disclose input-dependent behavior encoded in the schema's allOf conditions, such as the true-time/longitude and DST/timezone_id requirements, nor error behavior.

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 one dense but well-structured sentence: purpose first, return contents second, and exclusions last. There is no filler, though the density of domain jargon reduces readability.

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

Completeness2/5

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

For a high-complexity tool with 18 parameters, 11 required, conditional allOf/anyOf constraints, and no output schema, the description covers purpose and output scope but omits how to satisfy the input conditions. Missing guidance on true time/longitude, DST/timezone, and the two timezone alternatives leaves significant room for incorrect invocation.

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

Parameters2/5

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

There are 18 parameters with only 6% schema description coverage, and the description adds no per-parameter meaning. The phrase '完整显式出生民用时刻' hints that all birth-time fields must be explicit, but nothing explains calendar_type, is_leap_month, split_zi_hour, use_true_time, apply_dst, or the choice between timezone_id and timezone_offset_minutes.

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 (计算) and resource (古法禄命年柱三元、纳音生旺落位) and enumerates return components such as 禄/命/身, 四柱, 胎元, 命宫, 身宫. It distinguishes itself from ziwei.calculate_chart by explicitly excluding 紫微十二人生宫 and ratings/predictions, though it does not explicitly contrast with bazi.calculate_chart.

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?

The negative scope ('不生成紫微十二人生宫、吉凶计数、总体评级或事件预测') implies when not to use the tool, such as for ratings or event predictions. However, it gives no positive when-to-use guidance and names no alternatives, so an agent must infer that this is for classical Lu Ming evidence rather than general bazi chart calculation.

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