Skip to main content
Glama

gyeokguk

Determine your Saju chart's governing structure based on classical Myeongli rules. Input birth date, time, and gender to receive the named pattern, body strength, and favorable element.

Instructions

Gyeokguk (格局, chart structure/pattern) determination. Reads the chart's governing structure from the day-master and month-branch by classical Myeongli rules. Returns the named pattern with its true/quasi grade (e.g. 편인격 · 가격), the body strength (신강/신약), supporting sub-patterns (e.g. 식상생재), the favorable element (yongshin), and the five-element distribution behind the judgment. Use for 'what is my gyeokguk', 'what's my chart pattern / structure', '내 격국이 뭐야'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
birthYesBirth date & time, 12 digits YYYYMMDDHHMM (e.g. 199001151030). Use 1230 for unknown time.
genderYesGender — 0: female, 1: male (CAFE convention).
nameNoOptional name. Affects some engine outputs; omit to use the default.
is_lunarNoOptional. true if the birth date is a lunar-calendar date (default false = solar).
is_leap_yearNoOptional. true if the lunar birth month is a leap month (윤달). Only meaningful with is_lunar=true.
option1NoOptional Rat-hour (자시) rule — 0: Ya-jasi/야자시 (default), 1: Jo-jasi/조자시.
option2NoOptional year-pillar season basis — 0: Ipchun/입춘 (default, standard practice), -1: Dongji/동지.
locNoOptional birthplace region ID for overseas births (24Plus world-city ID). Omit for Korea.
time_unknownNoOptional. true if the birth time is unknown — the chart header marks the hour pillar as estimated. Pair with HHMM=1230.
Behavior4/5

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

With no annotations provided, the description fully describes what the tool returns: named pattern with grade, body strength, sub-patterns, favorable element, and five-element distribution. It discloses the behavioral outcome without 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?

The description is a single, well-structured paragraph that defines the term, explains the output, and gives usage examples. Every sentence adds value with no redundancy.

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?

Despite no output schema, the description details what the tool returns. With 9 parameters (2 required) and a specialized domain, the description provides sufficient context for an agent to decide when to use this tool versus siblings.

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?

All 9 parameters have descriptions in the input schema (100% coverage). The description adds value by explaining the purpose of the tool and its output, but does not add per-parameter details beyond the schema. 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 the tool's purpose: determining Gyeokguk (chart structure/pattern) using classical Myeongli rules. It explains what it returns (named pattern, grade, body strength, etc.) and provides example queries. It is distinct from sibling tools like saju_chart or yongshin_candidates.

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?

The description gives explicit usage examples ('Use for 'what is my gyeokguk''), making it easy for an agent to know when to use this tool. It does not explicitly mention when not to use alternatives, but the specificity of the task implies it.

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/dangamsoft/cafe-mcp'

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