Ancient Echoes MCP

Dong Gong Election

election.preview_donggong

Read-only

Resolves a Beijing civil date and optional time against almanac day/month entries using solar-term and day-pillar boundaries, returning original-text matches for modern activities.

Instructions

按 YYYY-MM-DD 北京时间民用日期、民用午夜日界、精确到秒的节令月界、日干支和值日匹配《董公選要覽》月日条文；时刻只影响交节月界，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_donggong"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	排除 1582-10-05 至 1582-10-14；0001–9999 范围内的 YYYY-MM-DD 北京时间民用日期；不得包含时分、时区或 UTC offset
`time`	No	北京时间（UTC+8）HH:mm；只用于精确到秒的节令月界，不改变民用日期日柱；省略时固定按 12:00 并留痕
`notes`	No
`locale`	No
`question`	No
`activity_type`	No	可填现代事项；结果会区分产品别名与实际命中的古籍事项原词，未直接覆盖时返回 not_covered

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Nov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With only readOnlyHint supplied, the description carries real weight: it discloses the civil-midnight day boundary, that 23:00–23:59 does not roll to the next day's entry, that time only shifts the solar-term month boundary to the second, that alias-to-source-term tracing is returned, and that nothing is persisted. Only the failure/error behavior and result shape remain undisclosed.

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

Conciseness5/5

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

One semicolon-delimited sentence that front-loads the matching rule and then layers the edge-case rules in priority order. Dense but every clause carries distinct operational meaning, with no filler.

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?

No output schema exists, and the description only hints at the return value (alias-to-original-term tracking) without describing the overall result structure. Combined with unaddressed parameters and no sibling routing, the definition is adequate but incomplete for a 6-parameter tool.

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 reinforces date semantics (Beijing civil date, midnight boundary) and time semantics (only affects the term month boundary, defaults to 12:00 per the schema). It adds nothing for notes, locale, and question, which are undocumented in both schema and description, leaving meaningful gaps.

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 + resource: matching day entries from 《董公選要覽》 by civil date, day ganzhi, and day-duty. It names the source classic explicitly, which distinguishes it from other election.preview_* siblings (taisui, jianchu, xiu, wutu) by school/system, though it never says so directly.

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: an agent can infer this is the Dong Gong almanac look-up for a given date, but there is no explicit statement of when to prefer it over election.find_good_days or the other preview_* tools. No prerequisites or exclusions are given.

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

Deploy Server