Skip to main content
Glama
Sign In
x402-mcp

x402-mcp

Official
by x402node
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cn402_zhanbu_taiyi

Compute the Tai Yi divination chart (9-palace cosmic oracle) for a specified datetime to generate high-level forecasts using Chinese cosmic numerology.

Instructions

Tai Yi Shen Shu / 太乙神数 / Tai Yi divination / heavenly divination / national fate / Chinese cosmic numerology / 太乙九宫 / nine-palace cosmic oracle. Compute the Tai Yi divination chart (9-palace cosmic oracle) for given datetime, traditionally used for high-level forecasting.

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
datetimeNoDatetime YYYY-MM-DD HH:MM (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It explains the tool computes a chart for a given datetime, but lacks details on mutability, output format, or any side effects. The billing note adds marginal context.

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 several synonyms and a billing note, which adds clutter. It is not poorly structured, but could be more streamlined.

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 the complexity of Tai Yi divination and no output schema, the description lacks detail on the result format or interpretation. It covers the input and purpose adequately, but falls short for a complete understanding.

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 single optional datetime parameter, and the description reiterates it. The description does not add meaningful new detail beyond what the schema provides, meeting the baseline for high 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 clearly states it computes a Tai Yi divination chart for a given datetime, using multiple names and specifying 'nine-palace cosmic oracle'. It effectively distinguishes from sibling divination tools like liuren and liuyao by naming Tai Yi specifically.

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 mentions 'traditionally used for high-level forecasting' and 'national fate', implying a high-level scope, but does not explicitly state when to use this tool versus other divination methods or provide usage exclusions.

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

Deploy Server

Other Tools