Skip to main content
Glama
shunshi-liuyao-mcp

shunshi-liuyao-mcp

Official

castHexagram

Casts Liu Yao (I Ching) hexagrams by coin, manual lines, time, or number, returning original and changed hexagrams plus Najia, six relatives, six spirits, ruling lines, and hidden spirits.

Instructions

Return 本卦/变卦, 四柱, 纳甲, 卦宫, 六亲, 六神, 世应, 旬空 and 伏神. coin uses three coins six times; time/number are explicitly alternative methods. at is optional naive local ISO datetime; omitted uses current clock time in the IANA timezone. Manual lines must be six 0/1 from bottom to top; moving is positions 1–6. number requires exactly two positive integers. No true solar time correction; day changes at 23:00 (sect=1).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "castHexagram"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNo
linesNo
methodNocoin
movingNo
numbersNo
timezoneNoAsia/Shanghai

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does supply real behavioral detail: no true solar time correction, day boundary at 23:00 (sect=1), naive local ISO datetime handling, and default timezone Asia/Shanghai. Those are non-obvious semantics an agent could not get elsewhere. It omits one critical trait, though: the coin method is a random draw and the tool's output is not deterministic for a given input, which materially affects how an agent should present or retry results.

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?

The content is dense and mostly earns its place, but it is delivered as one semicolon-chained block front-loaded with untranslated output jargon rather than the action. Parameter constraints are interleaved with output and time semantics, so the agent must re-parse rather than scan. A single lead sentence stating what the tool does, followed by method and timing rules, would preserve all information with better structure.

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?

For a six-parameter tool with no annotations and no output schema, the description does cover output contents, method semantics, and the tricky time-handling rules. It falls short on determinism/randomness, the meaning of the 0/1 line values, and any error behavior when inputs are invalid or method-specific inputs are missing. Adequate to attempt a call, not fully sufficient to call it correctly in all modes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 do the work, and it addresses all six parameters: at (naive local ISO, defaults to current clock), lines (six 0/1 bottom-to-top), method (four named options with a summary of each), moving (positions 1-6), numbers (exactly two positive integers), and timezone (IANA, with a default). The main gap is the mapping of 0/1 to yin/yang and how lines interact with moving to produce 本卦 vs 变卦, which remains inferential.

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

Purpose3/5

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

The description opens with a list of outputs (本卦/变卦, 四柱, 纳甲, ...) rather than a plain statement that the tool casts an I Ching hexagram; the verb 'Return' describes the response, not the action. The method sentence ('coin uses three coins six times') implies the casting operation, but an agent unfamiliar with the terminology must infer the purpose from the name plus scattered clues. There are no siblings to differentiate against, so the bar is lower, but the purpose is still only implied.

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?

'time/number are explicitly alternative methods' tells the agent that four mutually exclusive methods exist and that coin is the default, which is genuine routing guidance. However, it never says when an agent should prefer time, number, or manual over coin, nor what to do when inputs for multiple methods are present. Preconditions (manual needs six 0/1, number needs two positive integers) are stated, but they are constraints rather than usage selection advice.

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