Skip to main content
Glama

cn402_zhanbu_digit-method

Derive a divinatory hexagram or lucky number interpretation by inputting 3-6 random digits, using folk numerology for fortune telling.

Instructions

Number divination / 数字占卜 / numerology oracle / digit-based fortune telling / lucky number derivation / Chinese number prediction. Take 3-6 random digits and derive a divinatory hexagram or interpretation using folk numerology.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
digitsYesComma-separated 3-6 positive integers, e.g. 7,3,5 (required)
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that the tool uses folk numerology and derives a hexagram, and mentions a vague price ('unknown on Base'). However, it does not describe the response format, rate limits, or behavior for invalid input, leaving significant gaps.

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 description opens with a list of synonyms ('Number divination / 数字占卜 / numerology oracle / ...') which is repetitive and wastes space. The core instruction is clear, but the synonyms could be trimmed to improve conciseness.

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 and no annotations, the description adequately conveys the purpose and input but lacks details on the output format (hexagram, interpretation) and pricing implications. It provides sufficient context for basic usage but not full completeness.

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% for the sole parameter 'digits', so baseline is 3. The description adds that digits should be '3-6 random digits' and are used to 'derive a divinatory hexagram or interpretation', which provides context but mostly restates schema information.

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 explicitly states it is a 'Number divination / numerology oracle / digit-based fortune telling' tool that takes 3-6 digits and derives a divinatory hexagram or interpretation. This clearly distinguishes it from sibling tools like 'iching_coin' or 'cn402_zhanbu_liuren' which use different methods (coin toss, six ren).

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention any prerequisites, exclusions, or comparative advantages over other divination tools among the siblings.

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