Skip to main content
Glama
Sign In
Ancient Echoes MCP

Ancient Echoes MCP

by FlamesCN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Jian Chu Twelve Officers

election.preview_jianchu
Read-only

Query Jianchu day officers, matching twelve celestial gods, and lunar-go sect 2 daily dos/don'ts for a Beijing civil date, using precise solar-term boundaries and exact activity-term matching.

Instructions

按严格 YYYY-MM-DD 北京时间民用日期、民用午夜日界与精确节令月界（精确到秒）查询建除十二值星、同口径十二天神及 lunar-go sect 2 日宜忌；23:00–23:59 不提前换日，时刻只影响交节月界，事项只按完整原词命中；不保存记录。

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": "<date>"
    },
    "name": "election.preview_jianchu"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes排除 1582-10-05 至 1582-10-14；0001–9999 范围内的 YYYY-MM-DD 北京时间民用日期；不得包含时分、时区或 UTC offset
timeNo北京时间（UTC+8）HH:mm；只用于精确到秒的节令月界，不改变民用日期日柱；省略时固定按 12:00 并留痕
notesNo
localeNo
questionNo
activity_typeNo字段整体与日宜忌条目原词精确匹配；不拆词、不匹配子串、不作同义词映射

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior4/5

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

Beyond readOnlyHint=true the description discloses concrete behavior: the 23:00–23:59 window does not roll the day, time affects only the solar-term month boundary, matching is whole-word only with no synonym mapping, and nothing is persisted (不保存记录). These are non-obvious boundary semantics an agent could not get from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

There is no filler, but the whole definition is one long run-on clause chain separated by semicolons, and it opens with date-format rules rather than the core verb+resource. The agent must read to the middle of the sentence to learn what is actually returned.

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 and six parameters, the description should say more about the shape of the result (what fields a 值星/天神/宜忌 payload contains) and about the three unexplained optional parameters. It is adequate for a read-only lookup but leaves real gaps for an agent composing the call.

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 50%; the description adds real meaning for date (civil-date convention, no time component), time (used only for second-precision solar-term boundaries, defaults to 12:00), and activity_type (exact whole-word hit). However, notes, locale, and question are undocumented in both schema and description, so it does not fully compensate for the coverage gap.

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 gives a specific verb (查询) and names the exact resources returned: 建除十二值星, 同口径十二天神, and lunar-go sect 2 日宜忌. That is far more precise than the sibling election.* tools' names alone, though it never explicitly contrasts itself with neighbors such as election.preview_taisui or almanac.get_day.

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

Usage Guidelines2/5

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

It states usage constraints (strict Beijing civil date, no day advance during 23:00–23:59, exact-word activity matching) but gives no guidance on when to pick this over the many sibling election/almanac tools. An agent must infer the selection criteria from the resource names alone.

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