Skip to main content
Glama

cn402_iching_list

Retrieves the complete list of 64 I Ching hexagrams with names, numbers, and King Wen sequence order. Provides a full Yijing catalog for divination or study.

Instructions

I Ching 64 hexagrams full list / all Yijing gua / hexagram catalog / King Wen sequence / 易经六十四卦目录 / 64 trigrams pairs. Return all 64 I Ching hexagrams with name, number, and traditional sequence.

Price: unknown on Base (auto-paid in USDC).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations exist, so the description carries the full burden. It mentions 'Price: unknown on Base (auto-paid in USDC),' indicating potential cost. However, it lacks other behavioral details such as authentication requirements or rate limits.

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

Conciseness2/5

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

The description is verbose with redundant synonyms and Chinese translations (e.g., 'I Ching 64 hexagrams full list / all Yijing gua / hexagram catalog / King Wen sequence / 易经六十四卦目录 / 64 trigrams pairs'). This could be streamlined to a single clear sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description briefly mentions what is returned (name, number, sequence). It is minimally adequate but could elaborate on the output structure (e.g., array of objects).

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?

The tool has no parameters, and the input schema is empty with 100% coverage. The description adds no parameter info, but the baseline for zero parameters is 4, as no further clarification is needed.

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 it returns all 64 I Ching hexagrams with name, number, and traditional sequence. It specifies the resource (full list) and distinguishes from sibling tools like iching_hexagram or iching_divine that focus on specific hexagrams or divination.

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 implies usage via terms like 'full list' and 'catalog,' contrasting with more specific iching tools. However, it does not explicitly state when to use this tool over alternatives, nor does it provide exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/x402node/x402-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server