Skip to main content
Glama

I Ching MCP Server by RoxyAPI

by com.roxyapi

List all 64 hexagrams - I-Ching hexagram catalog API

get_iching_hexagrams
Read-only

Browse all 64 I-Ching hexagrams from the Book of Changes with their Chinese names, English translations, and trigram compositions. The hexagrams are ordered by the traditional King Wen sequence used in I-Ching divination for 3,000 years. Each hexagram represents a unique life situation combining two trigrams (Heaven, Earth, Thunder, Wind, Water, Fire, Mountain, Lake) into profound wisdom for decision-making and self-understanding.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoResponse language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English.en
limitNoMaximum items to return per page. Range: 1-64, default 20.
offsetNoNumber of items to skip for pagination. Default 0.
compactNoSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English."New value: +"Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns English."
    • changedInput schema / properties / lang / enum
      Previous value: -[
-  "en",
-  "tr",
-  "de",
-  "es",
-  "hi",
-  "pt",
-  "fr",
-  "ru"
-]New value: +[
+  "en",
+  "tr",
+  "de",
+  "es",
+  "hi",
+  "pt",
+  "fr",
+  "ru",
+  "zh-Hans",
+  "zh-Hant"
+]
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
    • changedInput schema / properties / compact / description
      Previous value: -"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."New value: +"Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {\"__cols\":[names],\"__rows\":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens."
  3. Changed1 schema field changed
    • changedInput schema / properties / offset / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / compact / description
      Previous value: -"Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false."New value: +"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."
  5. Changed1 schema field changed
    • addedInput schema / properties / compact
      Added value: +{
+  "default": false,
+  "description": "Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false.",
+  "type": "boolean"
+}
  6. 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 readOnlyHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds useful behavioral context: the result contains Chinese names, English translations, trigram compositions, and follows the traditional King Wen ordering. This goes beyond the schema and annotations by describing the catalog's organization and content.

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 first two sentences front-load the essential details: what is returned, what fields are included, and the ordering. The final sentence about 'profound wisdom' is a rhetorical flourish that does not help an agent select or invoke the tool, but it does not significantly bloat the description. Overall the description is compact and well-structured.

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?

For a simple read-only catalog endpoint with complete schema documentation, the description covers the main expected content and ordering. There is no output schema, but the description names the key fields, and the query parameters are fully documented elsewhere. A slightly richer mention of pagination defaults would be nice, but it is not essential for correct invocation.

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 all four parameters (lang, limit, offset, compact) are already fully documented in the schema. The description adds no parameter-specific guidance beyond the high-level 'browse all' framing, which is acceptable given the schema's completeness. This is the baseline 3.

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 states a specific verb ('Browse') and resource ('all 64 I-Ching hexagrams') and clearly distinguishes this catalog tool from sibling tools like get_iching_hexagrams_random or get_iching_hexagrams_lookup by emphasizing the complete set and King Wen ordering. The title and first sentence together make the tool's scope immediately obvious to an agent.

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 intended use case is implied by 'Browse all 64' and 'catalog' — an agent can infer this is for listing the full catalog rather than fetching one hexagram or a random one. However, the description never explicitly says when to prefer this over siblings or when not to use it, so the guidance is implicit rather than stated.

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

All I Ching MCP Server by RoxyAPI toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

Several tools have overlapping functionality: get_iching_hexagrams_random, post_iching_daily, get_iching_cast, and post_iching_daily_cast all return hexagram readings with interpretation, and their boundaries are subtle. The lookup variants are distinguishable, but agents could easily pick the wrong reading or casting tool.

Naming Consistency4/5

Most tools follow a clear get_iching_<resource> pattern with readable modifiers. However, the post_ prefix in two tools breaks the otherwise uniform get_ style even though all tools are fundamentally retrieval or generation endpoints.

Tool Count4/5

Nine tools is within a reasonable range for an I Ching reference and divination server, and most add a distinct access mode. The daily/random and cast/daily_cast pairs introduce slight redundancy, making the set slightly fuller than necessary.

Completeness5/5

The surface covers the core oracle workflow: casting, daily readings, lookups by number or binary pattern, listing all hexagrams, and trigram reference. There are no obvious dead ends since returned hexagrams can be re-looked-up by number.

Resources