I Ching MCP Server by RoxyAPI

Cast daily reading with changing lines - I-Ching divination API

post_iching_daily_cast

Read-only

Cast a complete daily I-Ching reading using the traditional three-coin method with seeded randomness. Unlike the simple daily hexagram, this provides the full casting experience with line values (6-9), changing line positions, and the resulting hexagram if transformation occurs. Same seed + same date = same casting result. Perfect for I-Ching divination apps requiring authentic oracle experience with daily consistency.

Input Schema

Name	Required	Description	Default
`date`	No	Date for the reading in YYYY-MM-DD format. Defaults to today (UTC). Useful for viewing past daily readings or pre-generating future ones.
`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
`seed`	No	Optional seed for reproducible readings. Same seed + same date = same hexagram every time. Pass any unique identifier (userId, email hash, session token) to give each user their own hexagram for the day. Without a seed every caller receives the same shared hexagram of the day.
`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

Name	Required	Description	Default
`date`	Yes
`seed`	Yes
`lines`	Yes
`hexagram`	No
`changingLines`	No
`resultingHexagram`	No
`changingLinePositions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / seed / description

Previous value: -"Optional seed for reproducible readings. Same seed + same date = same hexagram every time. Pass any unique identifier (userId, email hash, session token). Omit for anonymous daily readings."New value: +"Optional seed for reproducible readings. Same seed + same date = same hexagram every time. Pass any unique identifier (userId, email hash, session token) to give each user their own hexagram for the day. Without a seed every caller receives the same shared hexagram of the day."

Changed3 schema fields changedSep 23, 2026

addedOutput schema / properties / hexagram / properties / binary
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / hexagram / properties / changingLines

Added value: +{
+  "items": {
+    "properties": {
+      "meaning": {
+        "type": "string"
+      },
+      "position": {
+        "type": "number"
+      },
+      "text": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "position",
+      "text"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / hexagram / required

Previous value: -[
-  "number",
-  "symbol",
-  "chinese",
-  "english",
-  "pinyin",
-  "upperTrigram",
-  "lowerTrigram",
-  "judgment",
-  "image",
-  "interpretation"
-]New value: +[
+  "number",
+  "symbol",
+  "chinese",
+  "english",
+  "pinyin",
+  "upperTrigram",
+  "lowerTrigram",
+  "judgment",
+  "image",
+  "interpretation",
+  "binary"
+]

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "changingLinePositions": {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "changingLines": {
+      "items": {
+        "properties": {
+          "meaning": {
+            "type": "string"
+          },
+          "position": {
+            "type": "number"
+          },
+          "text": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "position",
+          "text"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "date": {
+      "type": "string"
+    },
+    "hexagram": {
+      "properties": {
+        "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",
+        "upperTrigram",
+        "lowerTrigram",
+        "judgment",
+        "image",
+        "interpretation"
+      ],
+      "type": "object"
+    },
+    "lines": {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "resultingHexagram": {
+      "properties": {
+        "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",
+        "upperTrigram",
+        "lowerTrigram",
+        "judgment",
+        "image",
+        "interpretation"
+      ],
+      "type": "object"
+    },
+    "seed": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "date",
+    "seed",
+    "lines",
+    "changingLinePositions"
+  ],
+  "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

A4.1/5.0

Behavior4/5

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

Annotations already establish readOnlyHint and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: the three-coin method, seeded determinism (same seed + same date = same result), changing lines, and transformation output.

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 definition is front-loaded with the core purpose and then explains the distinction from the simpler sibling. The final sentence is slightly promotional but still useful for positioning; overall it is efficient with little waste.

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?

The tool has an output schema and full parameter descriptions, so the description does not need to explain return values. It adequately covers the casting method, determinism, and differentiation from the simpler daily tool, though it could more explicitly point to the sibling tool by name.

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 are already well documented. The description reinforces seed/date determinism but does not add syntax, format, or usage detail beyond what the schema provides.

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 and resource: cast a complete daily I-Ching reading using the traditional three-coin method. It explicitly distinguishes itself from the simpler daily hexagram by emphasizing line values, changing lines, and resulting hexagram transformation.

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 clearly positions the tool for users who need the full casting experience rather than the simple daily hexagram, and explains that daily consistency comes from the seed plus date. It does not explicitly name the sibling tool it replaces or give a hard rule for when not to use it, but the intended use case is clear.

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?