Skip to main content
Glama
Sign In

I Ching

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Hexagram

get_hexagram
Read-onlyIdempotent

Look up one of the 64 I Ching hexagrams (King Wen sequence) by its number (1-64) or by name (Chinese, pinyin, or the English gloss used in this pack). Returns the full hexagram: binary lines, upper/lower trigram, judgment, image, all six line texts, and keywords, each in original wording referencing James Legge’s 1899 translation as the public-domain source.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
nameNoHexagram name: Chinese characters, pinyin (with or without tone marks), or English gloss, e.g. "Qian", "乾", "Pure Yang".
numberNoKing Wen hexagram number, 1-64.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered; the description goes further by enumerating exactly what is returned (binary lines, trigram, judgment, image, six line texts, keywords) and disclosing the Legge 1899 public-domain sourcing. It does not mention not-found behavior, which keeps it from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence: the verb and resource come first, then the lookup keys, then return contents and source. It is dense with parentheticals but every clause carries information; no filler.

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, the description must carry the return-value burden and does so thoroughly by listing every returned field. Minor gaps: what happens when no hexagram matches the input, and whether both parameters can be combined, are unaddressed.

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%, and the schema already documents both parameters with examples of Chinese characters, pinyin, and English gloss. The description restates the same accepted forms but adds no syntax, normalization, or precedence rules (e.g. what happens if both number and name are supplied). Baseline 3 is correct.

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 ("look up one of the 64 I Ching hexagrams"), names the King Wen sequence, and specifies the two lookup keys (number 1-64 or name). This makes it clearly distinguishable from search_hexagrams (broad search) and cast_i_ching (divination) without opening either schema.

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?

The lookup-by-number-or-name framing implies when to use it, but there is no explicit guidance on when to choose this versus search_hexagrams or cast_i_ching, and no exclusions or prerequisites stated. Usage is inferable but not spelled out.

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

All I Ching toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources