Skip to main content
Glama

cn402_zhanbu_qianzi

Draw a Chinese temple fortune slip (qiānzi) and receive a traditional interpretation with predictions for guidance.

Instructions

Chinese temple fortune slip / 求签 / 签文 / Chinese oracle slip / 抽签 / Guanyin temple lottery / 100 slips fortune / Chinese temple divination / lottery slip Chinese folk oracle. Draw a Chinese temple fortune slip (qiānzi) with traditional interpretation and prediction.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
templeNoTemple slip set (optional: 观音 关帝 etc.)
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral disclosure. It mentions 'drawing a fortune slip' and 'price unknown on Base' but does not explain mechanics, randomness, or any side effects. For a tool performing a divination draw, crucial behavioral traits are missing.

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 is relatively short but includes an excessive list of redundant synonyms (eight phrasings for the same concept). The price note ('unknown on Base') is out of place for a divination tool. While functional, the structure could be cleaner.

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

Completeness2/5

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

Given the tool's complexity (divination with optional temple parameter and no output schema), the description fails to explain what the user receives (e.g., slip text, interpretation, or prediction format). The mention of 'interpretation and prediction' is vague. The price note adds confusion rather than clarity.

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 single optional parameter 'temple' has schema coverage 100% with description 'Temple slip set'. The tool description adds concrete examples ('观音, 关帝'), providing extra meaning 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 clearly identifies the tool as drawing a Chinese temple fortune slip (qiānzi) with traditional interpretation and prediction. It provides multiple synonyms and names (求签, 签文, Guanyin temple lottery) that uniquely distinguish it from sibling divination tools like cn402_zhanbu_liuren or cn402_iching_divine.

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 given on when to use this tool vs alternatives. The description lacks any context about appropriate scenarios, exclusions, or comparisons to other divination tools among 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