Skip to main content
Glama
Sign In
Ancient Echoes MCP

Ancient Echoes MCP

by FlamesCN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Tai Yi Preview

divination.preview_taiyi
Read-only

Calculates deterministic Taiyi divination charts for a given Beijing civil datetime (1800–2100), returning year, month, day, or hour layouts with 72 ju, 16-palace stars/generals, and eight gates.

Instructions

按调用方冻结的 1800-2100 年北京时间民用时刻，计算太乙统宗 method 0 的年计/月计/日计/時計、72 局、十六宫星将、八门与主客定三算；23:00 子初切换次日日时干支，不按三算大小自动生成主客强弱、胜负或现实建议，不保存记录。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date_time": "<date_time>",
      "calculation_mode": "<calculation_mode>"
    },
    "name": "divination.preview_taiyi"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
localeNo
questionNo
date_timeYes调用方冻结的 1800-2100 年北京时间民用时刻，严格 YYYY-MM-DD HH:mm；不接受秒、T 分隔、前后空格、时区或 UTC offset
focus_areaNo
question_typeNo
calculation_modeYes

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?

Beyond readOnlyHint=true the description discloses behaviour an agent could not infer: the 23:00 子初 rollover changes the next day's 日/時干支, and the tool deliberately does not derive host/guest strength, win/lose calls, or real-world advice. '不保存记录' is consistent with the read-only annotation rather than contradicting it. Return format is not described beyond the enumerated calculation components.

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 broken by semicolons, front-loading the time anchor, then the computed artifacts, then the explicit exclusions. Nothing is redundant, though the packed phrasing makes it slower to parse than a short bulleted split would be.

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 usefully names what is produced and what is deliberately withheld, and it pins the supported time window. It still leaves the non-required parameters (question, question_type, focus_area, locale, notes) unexplained, so an agent cannot know how those inputs change the computation or the response language.

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?

Schema description coverage is only 14 percent (date_time alone is documented), so the description must carry the rest. It partially compensates by mapping calculation_mode to the four 年计/月计/日计/時計 outputs and by restating the frozen Beijing civil-time constraint, but question_type, focus_area, question, notes and locale are left entirely unexplained in both schema and description.

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 (计算) plus a named system and method variant (太乙统宗 method 0) and enumerates the outputs (年计/月计/日计/時計、72 局、十六宫星将、八门、主客定三算), which is far more specific than a generic 'preview divination'. It does not explicitly distinguish itself from the closely named sibling election.preview_taisui, so an agent must rely on the 太乙 vs 太岁 naming itself.

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?

Usage is only implied: the description establishes that the tool is a time-anchored Tai Yi calculation, and the explicit exclusions ('不按三算大小自动生成主客强弱、胜负或现实建议') function as a partial scope boundary telling the agent not to expect verdicts. There is no statement of when to pick this over the many sibling divination.preview_* methods, which is the main gap for a family this crowded.

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

Deploy Server

Other Tools