Skip to main content
Glama
Sign In
Ancient Echoes MCP

Ancient Echoes MCP

by FlamesCN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Month Suitability Search

election.find_good_days
Read-only

Find days in a given year and month whose almanac activities exactly match a specified term, returning direct suitability or avoidance evidence.

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>",
      "activity": "<activity>"
    },
    "name": "election.find_good_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
monthYes
activityYes与 lunar-go 当日宜忌完整术语做精确匹配，不拆词或映射同义词。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds two genuine behavioral constraints beyond that: it will not default to the server's current year/month, and it will not extrapolate good/bad fortune beyond literal matches. Those are exactly the kind of scope limits an agent needs to avoid misusing the output; only the response shape is left 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?

A single dense sentence with three semicolon-delimited clauses, each carrying distinct information (what is returned, date-source constraint, no-inference constraint). Nothing is redundant with the title or name.

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 should clarify what 'evidence' actually looks like — a list of days with matched terms? — and how a full month of matches is returned. It also says nothing about behaviour when the activity term matches nothing, which for a strict literal-match tool is a realistic failure path.

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 33% — only 'activity' is documented, and the schema already states the exact-match/no-synonym rule that the description echoes. The description does add that year and month must be explicitly supplied (no server-side defaulting), which compensates partially, but formats, ranges, and edge behaviour for those two integers remain unaddressed beyond the schema's min/max.

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 names a concrete verb and scope: returns whole-month almanac suitability evidence matched on an explicit year, month, and activity wording. The 'direct-hit evidence / no extra inference' phrasing implicitly distinguishes it from the sibling preview_* tools that do interpretive derivation, though no sibling is named explicitly.

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?

It implies the caller must supply explicit year/month rather than relying on the server's current date, which is usable guidance. However it never states when to pick this over almanac.get_day (single day) or election.preview_jianchu, leaving the agent to infer the division of labour from the name 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