Skip to main content
Glama

Totally Tarot Calculators

I Ching hexagram text, cited

get_iching_hexagram_text
Read-onlyIdempotent

Returns one of the 64 Zhouyi (I Ching) hexagrams by "hexagram", its number or its pinyin name (a toneless name shared by two hexagrams, such as "qian" for 1 and 15, is refused with both numbers as suggestions): trigrams, lines, and the judgement text (and one line text if asked) as printed in an edition with a preface dated 1591, each column with its archive page locator. Text not confirmed against a second copy is withheld.

The English meaning is AI-written and labelled; no human scholar has checked it. Each quoted column carries its archive locator.

Results include an attribution line and a permalink.

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": {
      "hexagram": "<hexagram>"
    },
    "name": "get_iching_hexagram_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineNoA line, 1 (bottom) to 6 (top), to add its text. Example: "2".
hexagramYesHexagram number in the received order, 1-64, or its pinyin name with or without tone marks. Example: "11" or "Tai".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / hexagram / description
      Previous value: -"Hexagram number in the received order, 1-64. Example: \"11\"."New value: +"Hexagram number in the received order, 1-64, or its pinyin name with or without tone marks. Example: \"11\" or \"Tai\"."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive, and the description layers on substantive behavior beyond them: unverified text is withheld rather than returned, the English gloss is AI-written and labelled as unchecked, quotations are tied to archive locators, and results carry an attribution line plus permalink. Ambiguous-identifier refusal is also disclosed.

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?

The lookup behavior and the ambiguity rule are front-loaded in the first sentence, so the important content is not buried. It loses a point for redundancy: 'each column with its archive page locator' and 'Each quoted column carries its archive locator' repeat the same fact, and the nested parenthetical in sentence one is dense.

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?

With no output schema and only two parameters, the description sufficiently covers what comes back (trigrams, lines, judgement, optional single line, attribution, permalink) and the one edge case an agent can hit (refused ambiguous name). Nothing needed to invoke it correctly is missing.

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 is 3; the description earns above it by explaining the collision rule for toneless pinyin (e.g. 'qian' covering 1 and 15) and by clarifying that only one line text is added when requested. That adds real semantics the schema alone does not convey.

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 ('Returns one of the 64 Zhouyi (I Ching) hexagrams') and enumerates the payload: trigrams, lines, judgement text, optional line text, each with an archive page locator. No sibling performs hexagram-text lookup, so the tool is trivially distinguishable from the computational tools around it.

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?

It tells the agent exactly how to address a hexagram (number 1-64 or pinyin with/without tones) and what happens on an ambiguous toneless name (refused, with both numbers suggested), which is real usage context. It stops short of naming an alternative or stating an explicit when-not-to-use condition; there is no textual rival among the siblings to route to.

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.

Resources