Skip to main content
Glama

Get Chinese Astrology

I Ching reading

cast_i_ching
Read-onlyIdempotent

Reads an I Ching hexagram from six line values, bottom line first: 6 is a changing Yin line, 7 a Yang line, 8 a Yin line and 9 a changing Yang line. Without line values it makes a random three-coin cast. Returns the primary and relating hexagrams, the changing lines and their classical 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_i_ching"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNoSix line values from 6 to 9, bottom line first. A cast is made when absent.

Output Schema

NameRequiredDescriptionDefault
itemYes
viewYes
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the non-obvious behavioral fact that the operation becomes nondeterministic when no lines are supplied, which is exactly the kind of context annotations cannot convey. It does not mention cost, latency, or text-source caveats, keeping it just short of a 5.

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?

Two sentences, front-loaded with the action and input encoding, then the fallback and the return contents. Every clause carries information; nothing is redundant with the title.

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

Completeness5/5

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

For a single optional-parameter tool with a full output schema, the definition covers input encoding, the default behavior when input is absent, and a sketch of the return payload. An agent has everything needed to call it correctly on the first attempt.

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 coverage is 100%, so the baseline would be 3, but the description supplies meaning the schema lacks: what each integer 6/7/8/9 signifies (changing Yin, Yang, Yin, changing Yang) and the bottom-line-first ordering. That is genuine semantic value beyond the bare 6-9 range constraint.

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?

States a specific verb and resource ('Reads an I Ching hexagram from six line values') and pins down the exact input encoding plus the no-input fallback ('random three-coin cast'). It also names the outputs, so an agent can distinguish it from siblings like get_bazi_chart or get_zi_wei_chart without opening a schema.

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?

The description makes the selection condition explicit on the input side: supply six line values for a deterministic reading, omit them for a random cast. It does not discuss when to prefer this divination method over the sibling chart tools, but the sibling names denote different systems rather than competing alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.