Korean Four Pillars (Saju/BaZi) calculator: pillars, elements, ten gods, sinsal, luck cycles.
Deterministic Korean Four Pillars chart from birth date/time. Astronomically grounded (Meeus), true-solar-time corrected, historical Korea timezone aware. Returns pillars, five elements, ten gods, sinsal, and luck cycles as structured JSON.
| Name | Required | Description | Default |
|---|---|---|---|
| d | Yes | 일 | |
| m | Yes | 월 | |
| y | Yes | 출생 연도 (음양력 변환 신뢰범위 1900~2100) | |
| hour | No | 시 (24h, 기본 0) | |
| gender | Yes | 성별 (대운 방향 결정) | |
| isLeap | No | 음력 윤달 여부 | |
| minute | No | 분 (기본 0) | |
| calendar | No | 양력(solar) 또는 음력(lunar) | solar |
| longitude | No | 출생지 경도 (진태양시 보정, 기본 서울 126.978) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the burden, and it does so well by disclosing determinism, Meeus-based astronomical calculations, true-solar-time correction, historical Korea timezone awareness, and structured JSON output. It doesn't mention error handling or edge cases, but for a compute tool the disclosed behavioral traits are sufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is exactly two sentences, tightly packed with essential information, and leads with the core function. There is no redundancy or fluff; every phrase adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity and absence of an output schema, the description does a solid job of summarizing key return categories (pillars, elements, ten gods, sinsal, luck cycles) and the methodological nuances. It could be more explicit about output structure or potential errors, but the schema handles parameter constraints, making this adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
All 9 parameters already have detailed schema descriptions (100% coverage), so the baseline is 3. The description's mention of true-solar-time correction and timezone awareness adds some context, but much of this is already embedded in the schema (e.g., longitude description explicitly mentions the correction). Thus, the description does not significantly enhance parameter meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it computes a Korean Saju chart from birth date/time, listing specific outputs (pillars, five elements, ten gods, sinsal, luck cycles) and methodology. The verb 'Compute' paired with the resource 'Korean Saju' makes the purpose unambiguous, and it distinguishes itself from generic astrology tools through the detailed methodology.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Since there are no sibling tools, explicit alternatives are not needed. The description establishes clear context for when to use this tool—any time a deterministic, astronomically corrected Saju chart is needed—and implies it is the correct choice for such computations. It doesn't explicitly state exclusions or prerequisites, but the coverage is adequate given the absence of competing tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Deterministic Korean Saju / BaZi Four Pillars MCP. Day Master, five elements, compatibility.
Korean saju fortune MCP: natal chart, today/daily/yearly luck, compatibility, and saved profiles.
BaZi (Chinese Four Pillars) chart calculator. Structured chart data only, no predictions.
Generate BaZi charts from birth details. Explore Four Pillars, solar terms, and Luck Pillars for d…
Add one secure layer between your agents and this server.
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is unambiguous and clearly defined.
The single tool name 'compute_saju' follows a clear verb_noun convention and is descriptive. However, with only one tool, there is no established pattern to evaluate across the set.
One tool is on the border for a server of this scope. Though the tool is comprehensive for a saju calculator, a slightly richer set could be expected (e.g., separate tools for different calculation aspects).
The tool covers the entire domain of Korean saju calculation, returning all relevant outputs (pillars, elements, ten gods, sinsal, luck cycles). There are no obvious missing operations for a deterministic calculator.