korean-saju-calculator
Server Details
Korean Four Pillars (Saju/BaZi) calculator: pillars, elements, ten gods, sinsal, luck cycles.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.4/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool, naming consistency is trivially maintained.
The single tool directly and completely covers the server's stated purpose of computing Korean saju charts, making the count appropriate.
The tool returns all expected outputs (pillars, elements, gods, luck cycles) for the domain, leaving no obvious gaps.
Available Tools
1 toolcompute_sajuCompute Korean Saju (Four Pillars / BaZi)AInspect
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) |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses that the tool is deterministic, uses Meeus algorithms, true-solar-time correction, and historical timezone awareness. It does not mention side effects, auth needs, or rate limits, but as a computation tool, safety is implied.
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?
Two concise sentences, front-loaded with key information. No wasted words. The second sentence lists return components efficiently.
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?
The description covers inputs, process, and outputs. It mentions return as structured JSON listing major components. No output schema exists, so the description compensates well. Could mention error handling or edge cases, but overall adequate for the tool's complexity.
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?
Schema coverage is 100%, so the baseline is 3. The description adds value by explaining the astronomical grounding, true-solar-time correction, and timezone awareness, which enriches the meaning of parameters like longitude and calendar type. This goes beyond the schema descriptions.
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 the tool computes a Korean Four Pillars chart from birth date/time. It specifies that it is deterministic, astronomically grounded, and returns specific structured components. No sibling tools exist, so differentiation is not needed.
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?
The description implies usage for birth date/time based saju computation. It provides technical context (astronomical, timezone aware) but does not explicitly state when not to use or mention alternatives. However, given no siblings, the guidance is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
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
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.
Discussions
No comments yet. Be the first to start the discussion!