Skip to main content
Glama
Sign In

I Ching

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Hexagrams

search_hexagrams
Read-onlyIdempotent

Search the 64 I Ching hexagrams (King Wen sequence) by a free-text query matched against name (Chinese, pinyin, English gloss) and keywords. Returns every matching hexagram as a short summary (number, names, binary lines); use get_hexagram for the full text of any match.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
queryYesSearch text, e.g. "patience", "thunder", "withdrawal", "Qian".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds value beyond that by disclosing the return payload shape (number, names, binary lines) and that it returns 'every' match, which tells the agent to expect multiple results rather than a single best hit.

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?

Two sentences, zero filler, with the core capability front-loaded and the hand-off to get_hexagram trailing as the natural next step. Every clause carries information an agent needs.

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 no output schema, the description correctly compensates by summarizing the return fields, and it names the downstream tool. Slightly incomplete on edge behavior – whether matching is fuzzy or exact, whether results are capped – which matters for a free-text search with no result schema.

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, but the description genuinely adds meaning by enumerating the index being matched against (Chinese name, pinyin, English gloss, keywords). That tells the agent a colloquial English term or a romanized spelling is a valid query, which the schema alone does not convey.

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 (search), resource (the 64 I Ching hexagrams, King Wen sequence), and the fields matched (Chinese name, pinyin, English gloss, keywords). This distinguishes it cleanly from the sibling get_hexagram, which retrieves full text by identification rather than query.

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?

Explicitly routes the agent to get_hexagram for full text after a match, so the two-step workflow is clear. It stops short of stating when not to use search (e.g., when the hexagram number is already known), so it's clear context but not full when/when-not coverage.

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

All I Ching toolsInspect
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