Saju from Seoul | Korean Astrology

Calculate Saju chart

calculate_saju

Read-only

Primary entry tool. Compute Korean Four Pillars from a Gregorian birth date: pillars (년월일시), Day Master, Five Elements, zodiac animal. Use when the user mentions 사주, Four Pillars, birth chart, pillars, 오행, 일간, or gives Y/M/D. Optional hour (0–23 local) completes the hour pillar; omit if unknown. Output: parse JSON from result_json.

Input Schema

TableJSON Schema

Name	Required	Description
`day`	Yes	Birth day of month.
`hour`	No	Local clock hour (0–23) for the time pillar; omit if unknown.
`year`	Yes	Birth year in the Gregorian calendar.
`month`	Yes	Birth month (1–12).
`gender`	No	Optional; included in chart metadata only.
`minute`	No	Birth minute (0–59); used with hour for LMT correction and 시진 boundary.
`country`	No	Birth country code. KR applies -32min LMT correction.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result_json`	Yes	JSON string of the tool result; parse for structured fields.

TDQS

A4.3/5.0

Behavior4/5

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

Annotations indicate readOnlyHint=true, destructiveHint=false, openWorldHint=false. Description adds context (Gregorian emphasis, optional fields, output format) without contradicting annotations. No annotation contradiction.

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

Conciseness4/5

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

Description is a single paragraph with front-loaded purpose. Every sentence adds useful information. Could be slightly more structured but is concise and effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 7 parameters (3 required), full schema coverage, and an output schema, the description covers purpose, usage, optional parameters, and output format. It is complete for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 7 parameters have schema descriptions (100% coverage). Description adds value by explaining that hour completes the hour pillar and that minute and country affect LMT correction. This goes beyond the schema.

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 Korean Four Pillars from a Gregorian birth date, listing specific outputs (pillars, Day Master, Five Elements, zodiac animal). It distinguishes itself from sibling tools like check_compatibility and get_day_master by being the primary entry tool.

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?

Description provides explicit triggers: mentions of 사주, Four Pillars, birth chart, etc., or when given Y/M/D. It also explains that hour is optional. Lacks explicit when-not-to-use instructions, but is clear enough.

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

All Saju from Seoul | Korean Astrology tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: calculating a chart, comparing two charts for compatibility, explaining a day master stem, and listing all stems and branches. No overlap or confusion.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: calculate_saju, check_compatibility, get_day_master, list_stems_and_branches.

Tool Count5/5

4 tools is well-scoped for the domain of Korean astrology, covering the core operations without being too few or excessive.

Completeness4/5

The set covers calculation, compatibility, day master explanation, and reference data. Missing a dedicated tool for interpreting individual pillars or providing detailed element breakdowns, but the core workflows are covered.

Resources

Need Help?