Skip to main content
Glama

Chart structure (格局)

gyeokguk
Read-onlyIdempotent

Analyze a Saju/BaZi birth chart to identify its classical pattern and grade, body strength, sub-patterns, and supporting elements. Use it to answer 'What is my chart pattern?' or '내 격국'.

Instructions

Gyeokguk (格局) chart structure by classical rules: named pattern and grade, body strength (strong/weak), sub-patterns, and the elements behind the judgment. Use for 'what is my chart pattern', '내 격국'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locNo24Plus world-city ID for births outside Korea.
sexNoSex at birth; sets the direction of the 10-year luck cycles. Required unless legacy 'gender' is given.
nameNoOptional display name.
birthYesLocal birth date and time. ISO 8601 'YYYY-MM-DDTHH:mm' (e.g. 1990-01-15T10:30) or legacy 12 digits 'YYYYMMDDHHmm'. Use 12:30 when the time is unknown and set time_unknown.
genderNoLegacy form of sex: 0 female, 1 male.
option1NoLegacy form of rat_hour_rule (1 = early).
option2NoLegacy form of year_boundary (-1 = winter_solstice).
calendarNoCalendar of the birth date. Default solar.
is_lunarNoLegacy form of calendar=lunar.
timezoneNoIANA time zone of the birthplace. Asia/Seoul is supported directly; for births elsewhere pass 'loc'.
is_leap_yearNoLegacy form of lunar_leap_month.
time_unknownNoBirth time unknown; the hour pillar is marked as estimated.
rat_hour_ruleNoRat-hour (子時) rule: 'late' 야자시 (default) or 'early' 조자시.
year_boundaryNoYear pillar boundary: 'lichun' 입춘 (default) or 'winter_solstice' 동지.
lunar_leap_monthNoLunar leap month (윤달). Only with calendar=lunar.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
toolYes
basisNoChart basis text ([기본정보]): pillars, calendar/season basis, luck-cycle start.
linksYes
engineYes
contractYes
disclaimerYes
input_echoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed30 schema fields changedv1.0.1
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / birth / description
      Previous value: -"Birth date & time, 12 digits YYYYMMDDHHMM (e.g. 199001151030). Use 1230 for unknown time."New value: +"Local birth date and time. ISO 8601 'YYYY-MM-DDTHH:mm' (e.g. 1990-01-15T10:30) or legacy 12 digits 'YYYYMMDDHHmm'. Use 12:30 when the time is unknown and set time_unknown."
    • addedInput schema / properties / calendar
      Added value: +{
      +  "description": "Calendar of the birth date. Default solar.",
      +  "enum": [
      +    "solar",
      +    "lunar"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / gender / anyOf
      Added value: +[
      +  {
      +    "const": 0,
      +    "type": "number"
      +  },
      +  {
      +    "const": 1,
      +    "type": "number"
      +  }
      +]
    • changedInput schema / properties / gender / description
      Previous value: -"Gender — 0: female, 1: male (CAFE convention)."New value: +"Legacy form of sex: 0 female, 1 male."
    • removedInput schema / properties / gender / enum
      Removed value: -[
      -  0,
      -  1
      -]
    • removedInput schema / properties / gender / type
      Removed value: -"integer"
    • changedInput schema / properties / is_leap_year / description
      Previous value: -"Optional. true if the lunar birth month is a leap month (윤달). Only meaningful with is_lunar=true."New value: +"Legacy form of lunar_leap_month."
    • changedInput schema / properties / is_lunar / description
      Previous value: -"Optional. true if the birth date is a lunar-calendar date (default false = solar)."New value: +"Legacy form of calendar=lunar."
    • changedInput schema / properties / loc / description
      Previous value: -"Optional birthplace region ID for overseas births (24Plus world-city ID). Omit for Korea."New value: +"24Plus world-city ID for births outside Korea."
    • addedInput schema / properties / loc / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / loc / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / lunar_leap_month
      Added value: +{
      +  "description": "Lunar leap month (윤달). Only with calendar=lunar.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / name / description
      Previous value: -"Optional name. Affects some engine outputs; omit to use the default."New value: +"Optional display name."
    • addedInput schema / properties / name / maxLength
      Added value: +40
    • addedInput schema / properties / option1 / anyOf
      Added value: +[
      +  {
      +    "const": 0,
      +    "type": "number"
      +  },
      +  {
      +    "const": 1,
      +    "type": "number"
      +  }
      +]
    • changedInput schema / properties / option1 / description
      Previous value: -"Optional Rat-hour (자시) rule — 0: Ya-jasi/야자시 (default), 1: Jo-jasi/조자시."New value: +"Legacy form of rat_hour_rule (1 = early)."
    • removedInput schema / properties / option1 / enum
      Removed value: -[
      -  0,
      -  1
      -]
    • removedInput schema / properties / option1 / type
      Removed value: -"integer"
    • addedInput schema / properties / option2 / anyOf
      Added value: +[
      +  {
      +    "const": 0,
      +    "type": "number"
      +  },
      +  {
      +    "const": -1,
      +    "type": "number"
      +  }
      +]
    • changedInput schema / properties / option2 / description
      Previous value: -"Optional year-pillar season basis — 0: Ipchun/입춘 (default, standard practice), -1: Dongji/동지."New value: +"Legacy form of year_boundary (-1 = winter_solstice)."
    • removedInput schema / properties / option2 / enum
      Removed value: -[
      -  0,
      -  -1
      -]
    • removedInput schema / properties / option2 / type
      Removed value: -"integer"
    • addedInput schema / properties / rat_hour_rule
      Added value: +{
      +  "description": "Rat-hour (子時) rule: 'late' 야자시 (default) or 'early' 조자시.",
      +  "enum": [
      +    "late",
      +    "early"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / sex
      Added value: +{
      +  "description": "Sex at birth; sets the direction of the 10-year luck cycles. Required unless legacy 'gender' is given.",
      +  "enum": [
      +    "female",
      +    "male"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / time_unknown / description
      Previous value: -"Optional. true if the birth time is unknown — the chart header marks the hour pillar as estimated. Pair with HHMM=1230."New value: +"Birth time unknown; the hour pillar is marked as estimated."
    • addedInput schema / properties / timezone
      Added value: +{
      +  "description": "IANA time zone of the birthplace. Asia/Seoul is supported directly; for births elsewhere pass 'loc'.",
      +  "type": "string"
      +}
    • addedInput schema / properties / year_boundary
      Added value: +{
      +  "description": "Year pillar boundary: 'lichun' 입춘 (default) or 'winter_solstice' 동지.",
      +  "enum": [
      +    "lichun",
      +    "winter_solstice"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "birth",
      -  "gender"
      -]New value: +[
      +  "birth"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "basis": {
      +      "description": "Chart basis text ([기본정보]): pillars, calendar/season basis, luck-cycle start.",
      +      "type": "string"
      +    },
      +    "contract": {
      +      "type": "string"
      +    },
      +    "data": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "label": {
      +          "type": "string"
      +        },
      +        "panel_count": {
      +          "type": "number"
      +        },
      +        "panels": {}
      +      },
      +      "required": [
      +        "panels"
      +      ],
      +      "type": "object"
      +    },
      +    "disclaimer": {
      +      "type": "string"
      +    },
      +    "engine": {
      +      "const": "cafe",
      +      "type": "string"
      +    },
      +    "input_echo": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "birth": {
      +          "type": "string"
      +        },
      +        "calendar": {
      +          "type": "string"
      +        },
      +        "sex": {
      +          "type": "string"
      +        },
      +        "timezone": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "birth",
      +        "calendar",
      +        "sex",
      +        "timezone"
      +      ],
      +      "type": "object"
      +    },
      +    "links": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "web": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "web"
      +      ],
      +      "type": "object"
      +    },
      +    "tool": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "engine",
      +    "contract",
      +    "tool",
      +    "input_echo",
      +    "data",
      +    "links",
      +    "disclaimer"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover the important behavioral profile: readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the 'classical rules' framing and output contents but no additional behavioral caveats such as handling unknown birth times or limitations. No contradiction with annotations.

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

Conciseness5/5

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

The description is two sentences, front-loads the tool's output, and then gives targeted query examples. There is no filler or redundant restating of the schema.

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 the rich input schema, strong annotations, and presence of an output schema, the description covers the core user intent well. The only notable gap is not naming or disambiguating against sibling chart tools, but the description is otherwise sufficient for a read-only lookup tool.

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?

The input schema has 100% description coverage across all 15 parameters, including legacy alternatives like 'gender' and 'option1'. The tool description does not add parameter-level meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource (gyeokguk chart structure) and lists concrete outputs: named pattern, grade, body strength, sub-patterns, and the elements behind the judgment. It is clear and actionable, but it does not explicitly differentiate this tool from siblings like saju_chart or ohaeng_balance.

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 use-case examples in both English and Korean ('what is my chart pattern', '내 격국'), which helps an agent select the tool. However, it does not mention when not to use it or name alternative tools for comparison.

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