Skip to main content
Glama
Sign In
Ancient Echoes MCP

Ancient Echoes MCP

by FlamesCN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Daily Almanac

almanac.get_day
Read-only

Query day-level Chinese almanac evidence—solar terms and auspicious/inauspicious activities—for an explicit Beijing civil date in YYYY-MM-DD format, without time or timezone input.

Instructions

按明确的 YYYY-MM-DD 北京时间民用日期查询黄历、节气与宜忌日级证据；不接受时分或时区，不返回用户提醒，不合成整体吉凶。

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": "almanac.get_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes排除 1582-10-05 至 1582-10-14；0001-01-01 到 9999-12-31 的北京时间民用日期；只接受 YYYY-MM-DD，不得附带时分、时区或 UTC offset。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

With readOnlyHint=true already supplied by annotations, the description still adds real behaviour: interpretation is limited to day-level evidence, no reminders are produced, and no aggregate auspiciousness verdict is synthesised — an important expectation-setting constraint. It says nothing about output shape or which fields the day-level evidence contains, which is the remaining gap.

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?

A single front-loaded sentence: purpose first, then the exclusions that matter. Every clause carries non-redundant information (date format, no time/timezone, no reminders, no holistic verdict) with no filler.

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

Completeness4/5

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

For a one-parameter, read-only tool with no output schema, the description covers what is queried and what is deliberately not returned, which is enough to call it correctly. The only shortfall is that it does not sketch the returned evidence structure, leaving the agent to discover the response shape empirically.

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 description coverage is 100% and the schema already spells out the YYYY-MM-DD pattern, the excluded 1582-10-05..14 range, and the Beijing civil-date rule. The description's date constraints largely restate that structured content, so it earns the baseline rather than extra credit.

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 (查询) plus precise resources (黄历、节气、宜忌日级证据) and pins the input to an explicit YYYY-MM-DD Beijing civil date, which separates it from divination/election siblings that synthesise judgments. It stops short of naming a specific sibling (e.g. almanac.get_solar_terms or almanac.convert_lunar_date) as the alternative, so the 5-level differentiation test is not fully met.

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

Usage Guidelines4/5

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

Explicit when-not rules are stated: no hours/minutes, no timezone, no user reminders, no synthesised overall 吉凶 — an agent can immediately tell that time-of-day or divination-style requests belong elsewhere. It does not name where those requests should go, so the routing is only half-specified.

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