Skip to main content
Glama
Sign In
x402-mcp

x402-mcp

Official
by x402node
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cn402_bazi_dayun

Determine your lifelong 10-year Major Luck Cycles (Da Yun) in Chinese astrology. Input birth datetime and gender to output gan-zhi pillars and start ages.

Instructions

Major Luck Cycles / 大运 / Da Yun / BaZi 10-year fortune periods / Chinese astrology life cycles / major luck pillars. Compute the lifelong sequence of 10-year major luck cycles, each with gan-zhi pillar and start age.

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "datetime": "<datetime>",
      "gender": "<gender>"
    },
    "name": "cn402_bazi_dayun"
  }
}

Input Schema

NameRequiredDescriptionDefault
datetimeYesBirth datetime YYYY-MM-DD HH:MM (required)
genderYesM | F (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions output includes pillar and start age but does not disclose edge cases, error handling, or data sources. The price note is irrelevant to behavior.

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 includes multiple synonyms and a price note that adds no value for tool selection. It is not optimally concise; the core statement is clear but padded with unnecessary text.

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 should explain return format more thoroughly. It mentions 'each with gan-zhi pillar and start age' but lacks structure details. Adequate but not fully complete for agent invocation.

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 both parameters, and the description adds no additional meaning beyond the schema's descriptions. Baseline score of 3 is appropriate.

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 the tool's purpose: 'Compute the lifelong sequence of 10-year major luck cycles, each with gan-zhi pillar and start age.' It uses specific verbs and resource terms, and effectively distinguishes from sibling bazi tools by focusing on Dayun cycles.

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 on when to use this tool versus alternatives like cn402_bazi_full or cn402_bazi_sizhu. No prerequisites or context provided. The description only states functionality without usage direction.

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