I Ching MCP Server by RoxyAPI

by com.roxyapi

Overview Discussions Admin

Server Details

I Ching hexagram casts, 64 hexagram meanings and changing lines for AI agents.

Ownership verified

Status: Healthy
Uptime: 99.9% over 79 days
Last Tested: 2026-11-08 00:55
Transport: Streamable HTTP · MCP 2025-11-25
URL
ChatGPT: –
Claude: –

TDQS

A3.9/5.0

Scored 2026-10-24 05:55 across 9 tools

Disambiguation4/5

Most tools have clearly distinct retrieval strategies (cast, list, binary lookup, number lookup, trigram list/id). The main overlap is between get_iching_hexagrams_random and post_iching_daily, and between get_iching_cast and post_iching_daily_cast, which differ mainly by seeding/daily determinism rather than purpose.

Naming Consistency4/5

All tools share a clear get_iching_/post_iching_ prefix, giving a predictable family. However suffix conventions vary (lookup, number, random, id, cast, daily, daily_cast) and follow resource-then-modifier ordering rather than a strict verb_noun pattern.

Tool Count5/5

Nine tools is well-scoped for a domain with 64 hexagrams, 8 trigrams, and two casting methods. Each tool earns its place, covering distinct retrieval and casting operations without bloat.

Completeness4/5

Coverage is strong: list, binary lookup, number lookup, random, full cast, trigram list/ID, and daily variants. The only notable gap is the inability to look up a hexagram by Chinese/English name or keyword, forcing users to know its number or binary pattern.

Available Tools

9 tools

get_iching_castCast an I-Ching reading - Hexagram divination APIA

Read-only

Inspect

Generate an authentic I-Ching reading using the traditional three-coin casting method. Each of the six lines is determined by virtually tossing three coins, producing values 6-9 where 6 (old yin) and 9 (old yang) are changing lines. Returns the primary hexagram with full interpretation, the line values showing which lines are changing, and if any lines change, the resulting hexagram that the primary transforms into. Optionally provide a seed for reproducible castings. Perfect for divination apps, oracle features, and decision-making tools.

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
`seed`	No	Optional seed for reproducible castings. Same seed = same casting every time. Pass any unique identifier (userId, session token, question hash). Omit for random casting.
`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
`seed`	No
`lines`	Yes
`hexagram`	No
`resultingHexagram`	No
`changingLinePositions`	Yes

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already mark this as read-only and non-destructive. The description adds meaningful behavioral context: virtual three-coin tossing, line values 6-9, changing-line mechanics, transformation into a resulting hexagram, and reproducible castings via an optional seed. This goes well beyond the annotations without contradicting them.

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 description is three well-organized sentences that front-load the core purpose and casting method, then cover outputs and optional seed behavior. The final sentence about use cases is slightly generic but not wasteful, keeping the description appropriately sized.

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 the output schema and annotations, the description covers the essential behavior, return semantics, and the optional seed. It does not mention language or compact options, but those are fully documented in the schema, so the overall context is sufficiently complete.

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 the schema fully documents lang, seed, and compact. The description only touches on the seed ('Optionally provide a seed for reproducible castings'), which adds little beyond the schema's already explicit 'Same seed = same casting every time.' Baseline 3 is appropriate.

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 names a specific verb and resource: 'Generate an authentic I-Ching reading using the traditional three-coin casting method.' It also explains what the output contains and differentiates this casting tool from sibling hexagram/trigram lookup tools by emphasizing full reading generation 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 Guidelines4/5

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

It provides clear context for when to use the tool: 'Perfect for divination apps, oracle features, and decision-making tools.' It does not explicitly name alternative siblings or state when not to use it, but the intended use case is evident from the casting-focused description.

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

get_iching_hexagramsList all 64 hexagrams - I-Ching hexagram catalog APIA

Read-only

Inspect

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.

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
`limit`	No	Maximum items to return per page. Range: 1-64, default 20.
`offset`	No	Number of items to skip for pagination. Default 0.
`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
`limit`	Yes
`total`	Yes
`offset`	Yes
`hexagrams`	Yes

TDQS

A3.5/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 safety is covered. The description adds useful context about King Wen ordering and the included content fields, but does not add operational behaviors like pagination defaults or language fallback; those live in the schema.

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 description is short and front-loaded: the first sentence states the action and content, and the second adds ordering context. The third sentence is somewhat ornamental ('profound wisdom for decision-making') but not long enough to significantly hurt usefulness.

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?

With zero required parameters, a read-only annotation, and a full output schema, the description covers everything needed to invoke the tool correctly. The only real gaps are not mentioning sibling alternatives and a bit of nonessential prose in the final sentence.

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%: lang, limit, offset, and compact are all already documented with defaults, ranges, and examples. The description adds no parameter-level meaning, so the baseline 3 applies.

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 names a specific action ('Browse all 64 hexagrams') and resource, and the title reinforces the catalog scope. The 'all 64' framing distinguishes it from sibling lookup/number/random tools, though it never explicitly names those siblings, keeping it from a 5.

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 usage is implied: use this tool when you want the full King Wen-ordered catalog of all 64 hexagrams. However, there is no explicit when-to-use vs alternative guidance, such as pointing to get_iching_hexagrams_lookup or random for single-hexagram needs.

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

get_iching_hexagrams_lookupLookup hexagram by line pattern - I-Ching binary lookup APIA

Read-only

Inspect

Find an I-Ching hexagram by its binary line pattern. Provide 6 digits (0 or 1) representing broken (yin) and solid (yang) lines from bottom to top. Use this for custom divination interfaces where users input their own line configurations, or to find hexagrams matching specific trigram combinations. Example: "111111" returns Hexagram 1 (The Creative), "000000" returns Hexagram 2 (The Receptive).

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
`lines`	Yes	Six-digit binary pattern (0=yin/broken, 1=yang/solid) from bottom to top.
`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
`image`	Yes
`binary`	Yes
`number`	Yes
`pinyin`	Yes
`symbol`	Yes
`chinese`	Yes
`english`	Yes
`judgment`	Yes
`lowerTrigram`	Yes
`upperTrigram`	Yes
`changingLines`	Yes
`interpretation`	Yes

TDQS

A4/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, establishing safe read behavior. The description adds the bottom-to-top line order and worked examples like '111111' -> Hexagram 1, but does not discuss error handling, response shape, or edge cases. It is adequate but not rich.

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 well-structured sentences: purpose, usage context, and concrete examples. It is front-loaded and free of filler or redundant schema repetition.

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?

With rich schema coverage, an output schema, and safety annotations, the description covers the essential entry point and usage context. It could mention invalid-input behavior or explicitly route to sibling tools, but nothing critical is missing for invoking the tool 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?

The schema already documents all three parameters thoroughly, including the line pattern, language enum with fallback behavior, and compact output format. The description mostly repeats the lines format and adds example output mapping, which is useful but not additive beyond 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 opens with a specific action and target: 'Find an I-Ching hexagram by its binary line pattern.' It clarifies the input semantics and provides concrete examples, making it easy to distinguish from siblings like get_iching_hexagrams_number or get_iching_hexagrams_random.

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 explicitly identifies intended contexts: custom divination interfaces where users enter their own line configurations, and matching specific trigram combinations. It does not name sibling alternatives or state when not to use the tool, so it falls short of full routing guidance.

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

get_iching_hexagrams_numberGet hexagram by number - I-Ching hexagram detail APIA

Read-only

Inspect

Retrieve complete I-Ching hexagram details by King Wen sequence number (1-64). Returns the full hexagram with Chinese name, English translation, judgment text, image text, modern interpretations for general situations, love, career, and decision-making, plus all six changing line meanings. Use this to display detailed hexagram information after casting or for educational reference.

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
`number`	Yes	Hexagram number in King Wen sequence (1-64).
`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
`image`	Yes
`binary`	Yes
`number`	Yes
`pinyin`	Yes
`symbol`	Yes
`chinese`	Yes
`english`	Yes
`judgment`	Yes
`lowerTrigram`	Yes
`upperTrigram`	Yes
`changingLines`	Yes
`interpretation`	Yes

TDQS

A4/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, and the description aligns with a pure retrieval operation. The description adds useful content expectations but no additional behavioral caveats such as authentication, rate limits, or response-size implications.

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 sentences with no filler: it front-loads the core action, summarizes the valuable return content, and closes with concrete use cases. Every sentence earns its place.

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 the output schema, read-only annotations, and fully described parameters, the description covers what an agent needs to operate the tool. It adds use context ('after casting or educational reference'), though it could more explicitly relate this tool to sibling tools like get_iching_hexagrams_lookup.

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 the schema already documents number, lang, and compact comprehensively. The tool description only echoes the number range and does not add meaning beyond the schema, matching the baseline for full coverage.

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 ('Retrieve'), a specific resource ('I-Ching hexagram details'), and a precise access method ('King Wen sequence number'). It also enumerates the returned content, making the tool's function unambiguous and distinguishable from sibling lookup/random/cast tools.

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 gives clear positive usage context: display detailed hexagram information after casting or for educational reference. It does not explicitly name sibling alternatives or state when not to use this tool, so it stops short of full alternative routing.

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

get_iching_hexagrams_randomRandom hexagram - I-Ching hexagram picker APIA

Read-only

Inspect

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.

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

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

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.

get_iching_trigramsList all 8 trigrams - Bagua trigram catalog APIA

Read-only

Inspect

Retrieve all 8 I-Ching trigrams (bagua), the fundamental building blocks of hexagrams. Each trigram consists of three lines and represents a primal force of nature: Heaven (Qian), Earth (Kun), Thunder (Zhen), Wind (Xun), Water (Kan), Fire (Li), Mountain (Gen), and Lake (Dui). Understanding trigrams is essential for interpreting hexagram meanings, as each hexagram combines an upper and lower trigram.

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

Name	Required	Description
`total`	Yes
`trigrams`	Yes

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. The description adds useful behavioral context beyond the annotations by stating that the tool returns the complete set of all 8 trigrams and enumerates their names and elemental associations, which clarifies the response scope.

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 description is concise at three sentences and front-loads the core retrieval purpose. The second sentence enumerates the trigram names, which is valuable reference content, and the third provides relevant context without being overly verbose.

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 the tool's simplicity, full parameter schema, existing output schema, and read-only annotations, the description provides adequate context. The only minor gap is the lack of an explicit routing pointer to sibling tools for single-trigram lookups, but this does not prevent 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%, and both parameters (lang and compact) have thorough descriptions in the schema. The tool description itself adds nothing about parameters, so the baseline score of 3 is appropriate since the schema fully carries this burden.

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 opens with a specific verb and resource: 'Retrieve all 8 I-Ching trigrams (bagua)'. It clearly identifies this as the catalog/list tool for the full set of trigrams, and the follow-on explanation of trigrams as hexagram building blocks differentiates it from the hexagram-focused sibling tools.

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 description implies the tool is useful when an agent needs the foundational trigram catalog or is preparing to interpret hexagrams. However, it does not explicitly state when to use this tool versus siblings like get_iching_trigrams_id or get_iching_hexagrams, nor does it name alternatives or exclusions.

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

get_iching_trigrams_idGet trigram by number or name - Bagua trigram detail APIA

Read-only

Inspect

Retrieve a specific I-Ching trigram by its number (1-8) or English name (Heaven, Earth, Thunder, Wind, Water, Fire, Mountain, Lake). Returns complete trigram information including Chinese name, pinyin, element associations, core attributes, and symbolic meaning. Use this to understand the component trigrams of any hexagram.

Name	Required	Description	Default
`id`	Yes	Trigram number (1-8) or English name (Heaven, Earth, Thunder, Wind, Water, Fire, Mountain, Lake).
`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

Name	Required	Description
`animal`	Yes
`binary`	Yes
`number`	Yes
`pinyin`	Yes
`season`	Yes
`symbol`	Yes
`chinese`	Yes
`element`	Yes
`english`	Yes
`meaning`	Yes
`quality`	Yes
`bodyPart`	Yes
`attribute`	Yes
`direction`	Yes
`familyMember`	Yes

TDQS

A4.3/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 safety profile is covered. The description adds that the operation returns complete trigram details, but does not disclose behaviors beyond that; this meets the baseline but adds only modest additional transparency.

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 sentences with no filler. The primary retrieval action and accepted inputs are front-loaded, followed by the return content and the practical use case, every sentence earning its place.

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?

For a single-resource read operation with full annotation coverage, a complete input schema, and an output schema, the description covers all essential context. It explains what is retrieved, how to identify the resource, and why an agent would use it.

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 schema already documents all three parameters. The description adds explicit meaning for the id parameter by listing the exact English names and the 1-8 numeric range, which helps an agent construct valid calls even before reading 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?

Description states a specific verb and resource: retrieve a single trigram by number or English name, with the acceptable values enumerated. It is clearly distinguished from the sibling list tool get_iching_trigrams and the hexagram-focused siblings.

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 final sentence gives a concrete use case: understanding the component trigrams of any hexagram. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to select this tool over the list-style sibling.

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

post_iching_dailyDaily hexagram - Daily I-Ching oracle APIA

Read-only

Inspect

Receive a daily I-Ching hexagram for guidance and reflection. This endpoint uses seeded randomness to ensure the same seed gets the same hexagram on the same day, perfect for "Hexagram of the Day" features in oracle apps, meditation platforms, and daily wisdom tools. Returns the hexagram with judgment, image, and interpretations for love, career, decisions, and practical advice based on ancient Chinese wisdom from the Book of Changes.

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
`date`	Yes
`seed`	Yes
`hexagram`	Yes
`dailyMessage`	Yes

TDQS

A3.6/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 safety is covered. The description adds genuinely non-redundant behavior: seeded determinism (same seed + date = same hexagram), the shared default when no seed is supplied, and the returned content domains. It stops short of describing completeness of the interpretation set or defaults for date beyond what the schema says.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and seed behavior are front-loaded, which is good, but the second half carries promotional filler ('perfect for... meditation platforms and daily wisdom tools', 'ancient Chinese wisdom from the Book of Changes') that does not help an agent invoke the tool correctly.

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?

An output schema exists and annotations carry the safety profile, so the description needn't explain return shape. Combined with the seed-determinism explanation and default behavior, an agent has enough to call this correctly; only sibling routing is missing.

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 documented in detail, setting the baseline at 3. The description reinforces the seed concept ('same seed gets the same hexagram on the same day') but adds no syntax or format detail the schema lacks.

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 a specific verb and resource — 'Receive a daily I-Ching hexagram' — and explains the seeded-per-day determinism, which distinguishes it in spirit from the random/cast siblings. It never names get_iching_hexagrams_random or post_iching_daily_cast, so the differentiation is implicit rather than explicit.

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 gives context ('perfect for Hexagram of the Day features in oracle apps, meditation platforms') and explains the seed vs no-seed choice, which is useful usage guidance. However, it gives no explicit when-to-use/when-not or routing against the very close sibling post_iching_daily_cast or the random-hexagram sibling, leaving the agent to infer.

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

post_iching_daily_castCast daily reading with changing lines - I-Ching divination APIA

Read-only

Inspect

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.

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
`date`	Yes
`seed`	Yes
`lines`	Yes
`hexagram`	No
`changingLines`	No
`resultingHexagram`	No
`changingLinePositions`	Yes

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

2 tool updatesOct 22, 2026

Changedpost_iching_daily1 field changed

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

Changedpost_iching_daily_cast1 field changed

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

2 tool updatesSep 23, 2026

Changedget_iching_hexagrams2 fields changed
- addedInput schema / properties / offset / default
```
Added value: +0
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```

Changedpost_iching_daily_cast3 fields changed

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

1 tool updateSep 20, 2026
- Changedget_iching_hexagrams3 fields changed
  - removedInput schema / properties / offset / default
```
Removed value: -0
```
  - removedInput schema / properties / offset / minimum
```
Removed value: -0
```
  - changedInput schema / properties / offset / type
```
Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"
```

9 tool updatesSep 20, 2026

Changedget_iching_cast1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "changingLinePositions": {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "hexagram": {
+      "allOf": [
+        {
+          "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"
+        },
+        {}
+      ]
+    },
+    "lines": {
+      "items": {
+        "type": "number"
+      },
+      "type": "array"
+    },
+    "resultingHexagram": {
+      "allOf": [
+        {
+          "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"
+        },
+        {}
+      ]
+    },
+    "seed": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "lines",
+    "changingLinePositions"
+  ],
+  "type": "object"
+}

Changedget_iching_hexagrams1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "hexagrams": {
+      "items": {
+        "properties": {
+          "chinese": {
+            "type": "string"
+          },
+          "english": {
+            "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"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "limit": {
+      "type": "number"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "limit",
+    "offset",
+    "hexagrams"
+  ],
+  "type": "object"
+}

Changedget_iching_hexagrams_lookup1 field changed

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

Changedget_iching_hexagrams_number1 field changed

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

Changedget_iching_hexagrams_random1 field changed

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

Changedget_iching_trigrams1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "total": {
+      "type": "number"
+    },
+    "trigrams": {
+      "items": {
+        "properties": {
+          "attribute": {
+            "type": "string"
+          },
+          "binary": {
+            "type": "string"
+          },
+          "chinese": {
+            "type": "string"
+          },
+          "english": {
+            "type": "string"
+          },
+          "number": {
+            "type": "number"
+          },
+          "pinyin": {
+            "type": "string"
+          },
+          "symbol": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "number",
+          "symbol",
+          "chinese",
+          "english",
+          "pinyin",
+          "binary",
+          "attribute"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "total",
+    "trigrams"
+  ],
+  "type": "object"
+}

Changedget_iching_trigrams_id1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "animal": {
+      "type": "string"
+    },
+    "attribute": {
+      "type": "string"
+    },
+    "binary": {
+      "type": "string"
+    },
+    "bodyPart": {
+      "type": "string"
+    },
+    "chinese": {
+      "type": "string"
+    },
+    "direction": {
+      "type": "string"
+    },
+    "element": {
+      "type": "string"
+    },
+    "english": {
+      "type": "string"
+    },
+    "familyMember": {
+      "type": "string"
+    },
+    "meaning": {
+      "type": "string"
+    },
+    "number": {
+      "type": "number"
+    },
+    "pinyin": {
+      "type": "string"
+    },
+    "quality": {
+      "type": "string"
+    },
+    "season": {
+      "type": "string"
+    },
+    "symbol": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "number",
+    "symbol",
+    "chinese",
+    "english",
+    "pinyin",
+    "binary",
+    "element",
+    "attribute",
+    "familyMember",
+    "direction",
+    "bodyPart",
+    "animal",
+    "season",
+    "quality",
+    "meaning"
+  ],
+  "type": "object"
+}

Changedpost_iching_daily1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "dailyMessage": {
+      "type": "string"
+    },
+    "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"
+    },
+    "seed": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "date",
+    "seed",
+    "hexagram",
+    "dailyMessage"
+  ],
+  "type": "object"
+}

Changedpost_iching_daily_cast1 field changed

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

1 tool updateSep 19, 2026
- Changedget_iching_hexagrams_number1 field changed
  - changedInput schema / properties / number / type
```
Previous value: -"number"New value: +"integer"
```

9 tool updatesAug 25, 2026

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

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

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

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

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

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

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

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

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

9 tool updatesAug 17, 2026

Changedget_iching_cast2 fields changed

addedInput schema / examples
```
Added value: +[
+  {}
+]
```