mcp-ziwei

Overview Schema Source Related Servers Discussions Admin

Get Zi Wei Dou Shu Chart

get_ziwei

Calculate a Ziwei Doushu astrological chart from birth date, time, and gender. Returns 12-palace text analysis and chart image.

Instructions

생년월일·출생시각·성별을 받아 자미두수(紫微斗数) 명반을 계산한다. 12궁 + 주성/보좌성 + 사화(四化) 텍스트와 12궁 명반 PNG를 반환한다. iztro 기반, 결정론적.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "birthDate": "<birthDate>",
      "birthTime": "<birthTime>",
      "gender": "<gender>"
    },
    "name": "get_ziwei"
  }
}

Input Schema

Name	Required	Description	Default
`birthDate`	Yes	생년월일 (YYYY-MM-DD)
`birthTime`	Yes	출생시각 (HH:MM, 24시간) → 時辰 인덱스로 변환
`gender`	Yes	성별
`calendarType`	No	양력(solar) / 음력(lunar)	solar
`lang`	No	로케일 (기본 ko-KR)	ko-KR

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 19, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It states the tool is deterministic and based on iztro, but does not disclose safety (e.g., read-only or destructive), authentication needs, or potential side effects. The output format is mentioned but not detailed.

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 extremely concise with three sentences. The first sentence states the purpose, the second describes outputs, and the third adds technical context. No unnecessary words.

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 moderate complexity (5 parameters, 3 required, no output schema), the description covers the main purpose and outputs. It could mention return structure or usage limitations, but the schema handles parameters well. The lack of output schema is mitigated by describing outputs (text and PNG).

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?

Schema description coverage is 100%, so the baseline is 3. The description does not add significant meaning beyond the schema, only noting that birthTime is converted to a time index. It does not explain derivation details or constraints beyond what is in the JSON 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 that it calculates a Zi Wei Dou Shu chart based on birth date, time, and gender. It specifies the output (12 palaces, main stars, auxiliary stars, four transformations text, and PNG). The verb '계산한다' and resource '명반' are specific, and there are no sibling tools to differentiate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions it is based on iztro and deterministic, but does not provide guidance on when to use this tool versus alternatives. No sibling tools exist, so differentiation is not needed, but the lack of contextual usage advice keeps this at a mid score.

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

Deploy Server

Other Tools

get_ziweiA