I Ching MCP Server by RoxyAPI

Random hexagram - I-Ching hexagram picker API

get_iching_hexagrams_random

Read-only

Receive a random I-Ching hexagram with full interpretation. Perfect for daily oracle features, meditation prompts, or exploring the Book of Changes. Returns complete hexagram data including judgment, image, interpretations for love/career/decisions, and all six changing line meanings.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	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.	en
`compact`	No	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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`image`	Yes
`binary`	Yes
`number`	Yes
`pinyin`	Yes
`symbol`	Yes
`chinese`	Yes
`english`	Yes
`judgment`	Yes
`lowerTrigram`	Yes
`upperTrigram`	Yes
`changingLines`	Yes
`interpretation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "binary": {
+      "type": "string"
+    },
+    "changingLines": {
+      "items": {
+        "properties": {
+          "meaning": {
+            "type": "string"
+          },
+          "position": {
+            "type": "number"
+          },
+          "text": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "position",
+          "text"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "chinese": {
+      "type": "string"
+    },
+    "english": {
+      "type": "string"
+    },
+    "image": {
+      "type": "string"
+    },
+    "interpretation": {
+      "properties": {
+        "advice": {
+          "type": "string"
+        },
+        "career": {
+          "type": "string"
+        },
+        "decision": {
+          "type": "string"
+        },
+        "general": {
+          "type": "string"
+        },
+        "love": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "general",
+        "love",
+        "career",
+        "decision",
+        "advice"
+      ],
+      "type": "object"
+    },
+    "judgment": {
+      "type": "string"
+    },
+    "lowerTrigram": {
+      "type": "string"
+    },
+    "number": {
+      "type": "number"
+    },
+    "pinyin": {
+      "type": "string"
+    },
+    "symbol": {
+      "type": "string"
+    },
+    "upperTrigram": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "number",
+    "symbol",
+    "chinese",
+    "english",
+    "pinyin",
+    "binary",
+    "upperTrigram",
+    "lowerTrigram",
+    "judgment",
+    "image",
+    "interpretation",
+    "changingLines"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedAug 25, 2026

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"
+]

Changed2 schema fields changedAug 17, 2026

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."

Changed1 schema field changedJul 22, 2026

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."

Changed1 schema field changedJul 22, 2026

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"
+}

First observedJul 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint true and destructiveHint false, so the description adds value by specifying the return content (judgment, image, interpretations, changing lines). This goes beyond annotations but does not discuss randomness behavior or other side effects.

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?

The description is two concise sentences, front-loaded with the core action and wrapped up with return data. 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?

Given an output schema exists and the tool is simple, the description covers purpose, use cases, and return summary. It is adequate for an agent to invoke correctly.

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 coverage is 100% with full descriptions for both lang and compact. The description adds no parameter details, so it scores at the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Receive a random I-Ching hexagram' with a specific verb and resource, and mentions use cases. It distinguishes from siblings implicitly by the 'random' qualifier, but does not explicitly name alternatives.

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?

It provides context on when to use (daily oracle, meditation, exploration) but does not explicitly state when not to use or compare with sibling tools like get_iching_hexagrams_number.

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 tools Inspect

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

Need Help?