Skip to main content
Glama
White Whale Bazi & Liuyao Engine

White Whale Bazi & Liuyao Engine

cast_liuyao_hexagram

Cast a deterministic Three-Coin Jing Fang Najia Liuyao hexagram to answer a decision question, returning primary, nuclear, and changed hexagrams with Shi/Ying, Six Relatives, and Zhouyi texts.

Instructions

Cast a deterministic Three-Coin Jing Fang Najia (京房纳甲) Liuyao hexagram plate, outputting primary/nuclear/changed hexagrams, Eight-Palace Shi/Ying, Six Relatives, Six Beasts, Fushen (hidden spirits), Day/Month stem-branch Xunkong, and public-domain Zhouyi (周易) hexagram texts.

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": "cast_liuyao_hexagram"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity for True Solar Time stem-branch calendar context.北京
seedNoOptional deterministic seed string simulating 6 tosses of 3 bronze coins.
linesNoOptional 6 line values bottom-up (初爻->上爻): 6=老阴(动), 7=少阳(静), 8=少阴(静), 9=老阳(动).
questionNoConcrete decision question being evaluated.
cast_dateNoOptional Gregorian date YYYY-MM-DD of casting (defaults to current local date).
cast_timeNoOptional HH:MM time of casting (defaults to current local time).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that the cast is deterministic and enumerates the returned components, but it is silent on important behaviors such as precedence when both 'seed' and 'lines' are supplied, whether anything is persisted, and whether the tool is purely a read/compute operation.

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?

It is a single dense sentence that front-loads the action and then lists outputs; nothing is padding. The trailing enumeration is long but each item is informative rather than filler, so the density is justified.

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?

With no output schema and no annotations, the description does real work by enumerating the returned hexagram components, which is what an agent most needs before calling. The remaining gap is the lack of any note on how the optional seed, lines, and date/time parameters combine when several are supplied.

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%, so every one of the six parameters is already documented in the schema, making 3 the baseline. The description adds only the general notion of determinism and does not explain the seed-versus-lines interaction or how city affects the stem-branch context beyond what the schema says.

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 very specific resource: casting a deterministic Three-Coin Jing Fang Najia Liuyao hexagram plate. It then enumerates exactly what the plate contains (primary/nuclear/changed hexagrams, Eight-Palace Shi/Ying, Six Relatives, Six Beasts, Fushen, Xunkong, Zhouyi texts), which is far more precise than the tool name alone and clearly separates it from a bazi calendar tool.

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 by the divination vocabulary and the phrase 'decision question being evaluated'; there is no explicit statement of when to choose this over calculate_true_solar_bazi, nor any exclusion or prerequisite. An agent can infer it is the hexagram-casting tool, but must decide routing on its own.

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