Skip to main content
Glama
Ancient Echoes MCP

Ancient Echoes MCP

Luohou Shashi Calendar

election.lookup_luohou_shashi
Read-only

Query Luohou Shashi evidence by explicit Beijing civil date, returning daily year, season, and month direct hits plus two Shashi time segments for almanac calendar checks.

Instructions

按显式北京时间民用起始日期查询罗喉杀师日时证据日历,逐日返回年、季、月罗喉直接命中与两段杀师时;不混入九宫飞星、其他造葬禁忌、整体吉凶、事项适宜性或现实危险结论。

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": {
      "year": "<year>",
      "month": "<month>",
      "day": "<day>"
    },
    "name": "election.lookup_luohou_shashi"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYes
yearYes
monthYes
days_to_showNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds real context beyond it: the calendar basis is explicit Beijing civil time, output is returned day by day, and the tool deliberately refuses to fold in other divination systems or real-world risk conclusions. It stops short of stating any range/pagination behavior for the returned days.

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 but well-formed sentence: the query semantics come first, the return content second, the exclusions last. No filler, though the exclusion clause is long and could be trimmed without loss.

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, no annotations beyond read-only, and 0% parameter coverage, the description does well on return content and scope boundaries. It is still incomplete for correct invocation: the number of days returned, how the range is capped, and behavior at month/year boundaries are all left unexplained.

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 0%, so the description must compensate. It does clarify that year/month/day form an explicit Beijing-time civil start date, which is meaningful semantics beyond bare integers, and '逐日返回' implies a multi-day span. However, days_to_show (default 32, max 90) is never mentioned, leaving a quarter of the parameters undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (查询) and a specific resource (罗喉杀师日时证据日历), and bounds its scope precisely: per-day year/season/month Luohou direct hits plus two shashi time segments. It further separates itself from adjacent systems by explicitly excluding 九宫飞星, other 造葬禁忌, overall auspiciousness and suitability judgments, so an agent can tell what this tool is and is not.

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 implied by the exclusions — it is the tool for Luohou Shashi evidence only, not for general good-day or taboo queries — but no alternative sibling is named (e.g., election.find_good_days, election.preview_taisui) and there is no explicit when-to-use/when-not statement. The negative scoping is helpful but the agent must infer routing.

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