Skip to main content
Glama
Sign In
x402-mcp

x402-mcp

Official
by x402node
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cn402_bazi_qiwang

Evaluate the strength of the Day Master in a BaZi chart to determine if it is strong, weak, or balanced, informing luck cycle interpretation based on Chinese astrology.

Instructions

Day Master strength / 起旺 / 旺衰 / strong weak Day Master / BaZi prosperity decline / Chinese astrology birth chart strength evaluation. Evaluate strength of Day Master in a BaZi chart (strong/weak/balanced), affecting luck cycle interpretation.

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>"
    },
    "name": "cn402_bazi_qiwang"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden but only mentions pricing (unknown on Base, auto-paid in USDC). It does not disclose whether the tool is read-only, destructive, or any side effects.

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 contains redundant synonyms (Day Master strength / 起旺 / 旺衰) and a pricing note, making it somewhat verbose. However, it front-loads the purpose and is structurally acceptable.

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?

No output schema exists, and the description fails to specify the output format (e.g., strong/weak/balanced or numeric). For a simple evaluation tool, this omission makes it incomplete.

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 datetime parameter, and the description does not add extra meaning beyond what the schema provides (birth datetime). Baseline 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 evaluates Day Master strength (strong/weak/balanced) using a birth datetime, distinguishing it from sibling BaZi tools that provide full charts or other analyses. The verb 'evaluate' and resource 'strength of Day Master' are specific.

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_dayun. The description does not indicate prerequisites or scenarios where this tool is preferred.

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