MCP server for Korean Four Pillars (Saju / BaZi) astrology — calculate charts, Ten Gods, Yongshin, compatibility, and daily fortune in 10 languages. KASI-validated engine, free 100 req/day.
Four tools with complete input schemas and descriptions. Naming follows verb_noun pattern (saju_calculate, saju_interpret, saju_compatibility, saju_daily). Descriptions are substantive (100-200 chars), explaining what each tool computes and when to use it. All parameters have type definitions and descriptions. However, output schemas are not documented, LLMs cannot see what fields to expect from responses. Error handling is present but generic (API error + hint). No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite all tools being read-only. Parameter descriptions could be more prescriptive about constraints (e.g., 'Use -1 if hour unknown' is good, but no explicit validation guidance for edge cases like Feb 30).
Compute the Korean Four Pillars of Destiny (사주팔자 / Bazi) from a solar birthdate. Returns the year/month/day/hour pillars (heavenly stem + earthly branch, with hanja), the five-element distribution (wood/fire/earth/metal/water), the Day Master, and the zodiac animal.
Score two-person compatibility (궁합) from 0–100 based on both people's Saju. Returns the overall score and a breakdown (element balance, Day Master relation, branch harmony, branch clash) plus each person's Day Master and zodiac.
Daily fortune snapshot (0–100 score + advice) for a given Day Master and date. Provide the Day Master either as a Korean stem character (갑, 을, 병, 정, 무, 기, 경, 신, 임, 계) or an English alias (e.g. wood_yang, water_yin). The Day Master comes from a prior saju_calculate / saju_interpret call (day_master.stem).
Full Saju interpretation from a solar birthdate: the Four Pillars plus Ten Gods (십신), hidden stems, life stages, interactions, Yongshin (용신 / useful god), Daeun (대운 / luck pillars), and human-readable summaries in the requested language.
Output schemas not documented. LLMs cannot see what fields responses contain (e.g., does saju_calculate return 'pillars' or 'four_pillars'? Is 'day_master' an object or string?). This forces agents to guess field names for downstream operations.
No tool annotations. All four tools are read-only (no side effects), but readOnlyHint is not set. Agents cannot distinguish safe tools from destructive ones without explicit hints.
saju_compatibility has nested object parameters (person_a, person_b) with repeated lang fields. The lang field appears at both the nested level and top level, creating ambiguity about which takes precedence. Documentation should clarify precedence rules.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 60 | 2026-07-28+ | v2 |
Error handling is generic. toToolResponse() returns API error status + body, but does not categorize errors as retryable vs. user-fixable. A 401 hint is provided, but 400 (invalid date) and 429 (quota) lack recovery guidance.
Parameter descriptions use examples ('갑, 을, 병...') instead of formal constraints. The saju_daily day_master param lists Korean stems in the description but should use an enum or pattern to prevent hallucinated values.