AstroWay Astrology API (full catalogue)

I Ching Hexagram (DEPRECATED: use /iching/throw-coins)

astroway_esoteric_iching

Read-onlyIdempotent

DEPRECATED: legacy un-namespaced random hexagram cast. Superseded by the /iching/* namespace: /iching/throw-coins (seeded + reproducible), /iching/by-question, /iching/with-changing-lines, /iching/daily, /iching/lookup/{n}, all on the Wilhelm-Baynes hexagram set. Still works until its 2027-06-16 sunset, then removed. Casts a single I Ching hexagram (input ignored).

[Group: Esoteric] [Endpoint: POST /v1/iching] [Cost: 10 credits (Tier 1)] [⚠️ DEPRECATED — will be removed in a future API version. Avoid using.]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description	Default
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

Name	Required	Description	Default
`name`	No
`lines`	No
`number`	No
`chinese`	No
`trigrams`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedNov 7, 2026

removedOutput schema / properties / chinese / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / chinese / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / lines / anyOf

Previous value: -[
-  {
-    "items": {
-      "anyOf": [
-        {
-          "additionalProperties": {},
-          "properties": {
-            "isChanging": {
-              "anyOf": [
-                {
-                  "type": "boolean"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "isYang": {
-              "anyOf": [
-                {
-                  "type": "boolean"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "value": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            }
-          },
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "properties": {
+            "isChanging": {
+              "type": [
+                "boolean",
+                "null"
+              ]
+            },
+            "isYang": {
+              "type": [
+                "boolean",
+                "null"
+              ]
+            },
+            "value": {
+              "type": [
+                "number",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / name / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / number / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / number / type
```
Added value: +[
+  "number",
+  "null"
+]
```

changedOutput schema / properties / trigrams / anyOf

Previous value: -[
-  {
-    "items": {
-      "anyOf": [
-        {
-          "type": "number"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

First observedOct 5, 2026

TDQS

A3.9/5.0

Behavior2/5

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

The description adds genuinely useful behavior beyond the annotations: random cast, input ignored, 10-credit Tier 1 cost, POST /v1/iching endpoint, and a hard removal date. However, "random hexagram cast" is in tension with the supplied idempotentHint=true, since repeated identical calls cannot return identical results — an agent trusting the annotation would assume reproducibility that this tool does not offer. Normally this conflict would score 1; credit is retained only because the description is additive in every other respect.

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?

Deprecation and the migration pointers are front-loaded, which is the right priority ordering. There is minor redundancy — the deprecation is stated three times (title, first clause, footer warning), and the six-item namespace list is long, though each entry does carry differentiating information.

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 zero-required-param, output-schema-bearing tool, the definition covers purpose, alternatives, cost, transport, and lifecycle. The remaining gaps are whether fields/precision actually shape the response and whether changing lines are included, both of which affect result interpretation.

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%, so fields and precision are already documented, which sets the baseline at 3. The description's "(input ignored)" is meaningful new information about required inputs, but it is ambiguous against a schema that still exposes compact-mode fields/precision parameters whose effect on output is left unstated.

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 ("Casts a single I Ching hexagram") and explicitly positions itself against the sibling family: legacy un-namespaced vs. the /iching/* namespace tools. An agent can tell instantly this is the deprecated random-cast variant rather than throw-coins, by-question, or with-changing-lines.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-not-to-use ("DEPRECATED... Avoid using") plus named alternatives with their distinguishing traits (seeded/reproducible for throw-coins, daily, lookup/{n}, changing lines). It also gives the concrete sunset date (2027-06-16), so the agent knows the migration window rather than just "don't use it".

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

All AstroWay Astrology API (full catalogue) 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?