I Ching Hexagram MCP

Get Reading Context

get_reading_context

Read-onlyIdempotent

Deterministic reading context for a primary hexagram (1-64) and 0-6 ascending changing lines. Empty changing_lines returns the primary hexagram only; one or more changing lines add the resulting hexagram, the transition, and the changing-line texts. No divination is performed. Data © IChing.Rocks — attribution is a condition of the license terms: https://iching.rocks/mcp-terms.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`include`	No	Detail level, each nesting the previous: summary = identity, essence, url; core (default) = adds trigrams, judgment, image; lines = adds the six line texts; full = adds symbolic meaning and final comment.	core
`primary_id`	Yes	Primary hexagram number, 1-64 (King Wen).
`changing_lines`	Yes	Changing line numbers (1-6), strictly ascending, no duplicates. Empty for an unchanging reading.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`source`	No
`primary`	No
`resulting`	No
`transition`	No
`final_comment`	No
`changing_line_texts`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 8, 2026

changedInput schema / properties / include / default
```
Previous value: -nullNew value: +"core"
```

changedInput schema / properties / include / description

Previous value: -"Detail level: summary | core | lines | full. Default core."New value: +"Detail level, each nesting the previous: summary = identity, essence, url; core (default) = adds trigrams, judgment, image; lines = adds the six line texts; full = adds symbolic meaning and final comment."

Changed1 schema field changedJul 4, 2026

addedOutput schema / properties / final_comment

Added value: +{
+  "properties": {
+    "explanation": {
+      "type": "string"
+    },
+    "original_text": {
+      "$ref": "#/properties/primary/properties/judgment/properties/original_text"
+    },
+    "text": {
+      "type": "string"
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed3 schema fields changedJul 4, 2026
- addedOutput schema / properties / primary / properties / source / properties / attribution_line
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / primary / properties / trigram_above / properties / source / properties / attribution_line
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / source / properties / attribution_line
```
Added value: +{
+  "type": "string"
+}
```
First observedJul 3, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses determinism, the input-dependent behavior, the absence of divination, and the attribution/license requirement. This adds meaningful context about what the tool does and does not do.

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 three tightly written sentences. It front-loads the core purpose and behavior, then adds the licensing note. Every sentence earns its place with no redundancy or filler.

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?

Given the rich schema, output schema, and annotations, the description provides all necessary context: purpose, behavior under different inputs, determinism, and licensing. Nothing essential is missing for an agent to select and invoke the tool correctly.

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 adds value by explaining the effect of changing_lines: empty values return primary only, while non-empty values include the resulting hexagram and transition. It also reinforces the range and ordering constraints already present in the schema.

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 clearly states a specific function: 'Deterministic reading context for a primary hexagram (1-64) and 0-6 ascending changing lines.' It distinguishes itself from sibling tools by emphasizing the changing-lines behavior and clarifying that no divination is performed.

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?

The description provides clear behavioral guidance on when to use the tool: empty changing_lines returns the primary hexagram only; changing lines add resulting hexagram and transition. It implies the tool is for reading context rather than divination, though it does not explicitly name alternative sibling tools.

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

All I Ching Hexagram MCP 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?