Skip to main content
Glama
Sign In
x402-mcp

x402-mcp

Official
by x402node
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cn402_bazi_shensha

Compute all major auspicious and inauspicious stars (Shen Sha) in a BaZi chart from a birth datetime, including Tian Yi Gui Ren, Tao Hua, and Yi Ma.

Instructions

Shen Sha / 神煞 / BaZi auspicious and inauspicious stars / Chinese astrology spirit influences / Tian Yi Gui Ren 天乙贵人 / Tao Hua 桃花 / Yi Ma 驿马 / nobleman peach blossom traveling horse stars. Compute all major shensha (auspicious/inauspicious stars) appearing in a BaZi chart.

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_shensha"
  }
}

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?

No annotations are provided, and the description lacks behavioral details such as whether the tool returns only star names or also interpretations, or if it requires specific input formats beyond the datetime. The payment 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 is verbose with repetitive synonyms and examples. While it front-loads key terms, it could be more concise. The payment information is unnecessary for tool usage.

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 is provided, and the description does not explain what the output contains (e.g., list of stars, interpretations, or formatting). For a tool computing stars, this is insufficient for an agent to understand the result.

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?

Only one parameter 'datetime' with 100% schema coverage. The description does not add any extra meaning beyond the schema's 'Birth datetime YYYY-MM-DD HH:MM (required)'. Baseline 3.

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 computes all major shensha (auspicious/inauspicious stars) in a BaZi chart, using specific examples like Tian Yi Gui Ren, Tao Hua, Yi Ma. It distinguishes from sibling tools that compute other BaZi elements.

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. No mention of prerequisites or exclusions. The description is silent on context.

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