Yijing Bazi MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | The Node.js environment mode (e.g., 'production', 'development') | production |
| LOG_LEVEL | No | The logging level for the server (e.g., 'info', 'debug') | info |
| SERVER_NAME | No | The name of the MCP server | yijing-bazi-mcp-server |
| ENABLE_CACHE | No | Enable or disable caching functionality | true |
| SERVER_VERSION | No | The version of the MCP server | 1.0.0 |
| ENABLE_PERFORMANCE_MONITORING | No | Enable or disable performance monitoring | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| yijing_generate_hexagramC | 根据指定方法生成六爻卦象 |
| yijing_interpretC | 对卦象进行多层次解读 |
| yijing_adviseC | 基于卦象提供决策建议 |
| bazi_generate_chartC | 生成八字命盘 |
| bazi_analyzeC | 分析八字命盘 |
| bazi_forecastC | 预测未来运势 |
| combined_analysisC | 结合易经和八字进行综合分析 |
| destiny_consultC | 提供命理咨询服务 |
| knowledge_learnC | 学习易经和八字知识 |
| case_studyC | 分析易经和八字案例 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
The tools have some clear distinctions, such as between bazi_analyze (analyzing a birth chart) and yijing_interpret (interpreting hexagrams), but there is overlap in purpose. For example, bazi_forecast (predicting future luck) and destiny_consult (providing destiny consultation) could be confused as both involve future-oriented advice, and case_study (analyzing case studies) might overlap with combined_analysis (comprehensive analysis). Descriptions help differentiate, but ambiguity exists in the broader advisory functions.
The naming is mostly consistent with a clear pattern: most tools use a prefix like 'bazi_' or 'yijing_' followed by a verb_noun structure (e.g., bazi_analyze, yijing_generate_hexagram). However, there are minor deviations: case_study and knowledge_learn lack the prefix, and combined_analysis uses a different structure. Overall, the naming is readable and follows a predictable convention with only slight inconsistencies.
With 10 tools, the count is well-scoped for the server's purpose of Yijing and Bazi analysis. Each tool appears to serve a distinct role in the domain, such as chart generation, interpretation, forecasting, and learning. This number allows comprehensive coverage without being overwhelming, fitting typical expectations for a specialized server.
The tool set covers key aspects of Yijing and Bazi analysis, including generation (bazi_generate_chart, yijing_generate_hexagram), interpretation (bazi_analyze, yijing_interpret), forecasting (bazi_forecast), and advisory functions (yijing_advise, destiny_consult). Minor gaps might exist, such as lack of tools for historical data or advanced customization, but core workflows are well-covered, allowing agents to perform most essential tasks in this domain.