Skip to main content
Glama
Espivc

ming-metaphysics-mcp

by Espivc

ming_full_forecast

Combine BaZi, ZWDS, Feng Shui, and QMDJ engines into a single master forecast for a birth profile. Specify a year, goal, and question to focus the synthesis. I Ching requires a separate query.

Instructions

Run all four birth-data engines (BaZi + ZWDS + Feng Shui + QMDJ) for a birth profile and return an integrated Master-tier forecast. I Ching is excluded from bulk forecasts (it requires a specific question — use ming_iching_cast separately).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
birth_dateYesDate of birth in YYYY-MM-DD format.
birth_hourNoHour of birth in 24-hour format (0–23).
birth_locationNoCity and country of birth (e.g. 'Singapore, Singapore').
genderYes
forecast_yearNoThe year to forecast for. Range 1900–2200, defaults to current year. Affects BaZi luck pillar selection and ZWDS 流年四化 annual chart.
questionNoPrimary question to orient the synthesis (e.g. 'Is 2026 the right year to start a business?').
goalNoFocus domain for the synthesis. Maps to the /consult 'goal' parameter. Defaults to 'general'.general
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states it 'runs' the engines, without disclosing behavioral traits like read-only status, side effects, or permissions. Minimal transparency for a complex tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the main purpose, and the second sentence adds a crucial usage note. No unnecessary words.

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?

For a complex tool integrating four engines without an output schema, the description is too minimal. It does not explain what 'integrated Master-tier forecast' includes, nor any behavioral assumptions or expected output structure.

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 high (86%), so the schema already documents all parameters. The description adds context about I Ching exclusion but does not significantly enhance parameter meaning. Baseline 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 it runs four engines (BaZi, ZWDS, Feng Shui, QMDJ) and returns an integrated forecast. It distinguishes from siblings by explicitly excluding I Ching and directing to ming_iching_cast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides clear context for when to use (integrated forecast) and explicitly excludes I Ching, directing to a sibling. However, it lacks guidance on when to use this versus individual engine tools like ming_bazi_analyze.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Espivc/ming-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server