Skip to main content
Glama
Ancient Echoes MCP

Ancient Echoes MCP

Chuangong Twelve Gods

bazi.calculate_chuangong
Read-only

Calculates Chuangong Twelve Gods placements year by year from birth date/time and start year, returning Four Pillars, palaces, luck-cycle GanZhi, and birth-year-branch relations.

Instructions

按完整显式出生民用时刻和显式起始年份计算串宫十二神落位,逐年返回四柱、胎元、命宫、身宫与当步大运的干支落位及出生年支直接关系;不生成吉凶分、年份排名、医疗法律判断或事件预测。

Input Schema

NameRequiredDescriptionDefault
dayYes
hourYes
yearYes
monthYes
minuteYes
is_maleYes
latitudeNo
apply_dstYes按 IANA 历史规则把夏令钟表时手工回拨为标准时;请求与实际应用分别留痕
city_nameNo
longitudeNo
timezone_idNo
current_yearYes调用方显式指定的起始公历年份标签;服务端不读取当前年份
birth_countryNo
calendar_typeYes
is_leap_monthYes
split_zi_hourYes
use_true_timeYes
birth_place_typeNo
years_to_calculateNo
timezone_offset_minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description usefully adds that results are produced year-by-year and that no auspicious/inauspicious scores, year rankings, medical/legal judgments or event predictions are produced — a meaningful scope boundary that prevents downstream misuse. It stops short of covering performance, input validation behavior (e.g., true-time/DST requirements), or error conditions.

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?

A single dense sentence that front-loads the computation and then the return payload, followed by a clear exclusion clause. It is information-dense without filler, though the long semicolon-joined structure is somewhat hard to scan.

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

Completeness3/5

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

With no output schema, the description does describe the return shape (per-year pillars, taiyuan/minggong/shengong, luck-cycle placements), which is valuable. But for a 20-parameter tool with conditional requirements, it omits too much about input semantics to be considered complete.

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?

The schema has 20 parameters with only ~10% description coverage and complex conditionals (use_true_time requires longitude/latitude; apply_dst requires timezone_id), yet the description only refers generically to 'explicit birth civil time' and 'explicit starting year'. Gender (is_male), split_zi_hour, calendar_type, leap month, and the timezone options are given no meaning in the description, leaving most of the input surface undocumented.

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?

The description states a specific verb and resource: 'calculate Chuangong Twelve Gods placements' (计算串宫十二神落位), and names the returned artifacts (four pillars, taiyuan, minggong, shengong, current major-luck stems/branches). It does not explicitly contrast with the sibling bazi.calculate_chart, so an agent must infer the difference from the resource name alone.

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?

Prerequisites are implied by 'complete explicit birth civil time and explicit starting year' (nothing defaulted, all inputs must be supplied), which is real usage signal. However, there is no statement of when to choose this over bazi.calculate_chart or bazi.calculate_luming; the negative clause concerns output content (no scores, rankings, predictions), not tool selection.

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