mcp-astrology

Overview Schema Source Related Servers Discussions Admin

Get Natal Chart

get_natal_chart

Calculate a Western astrology natal chart using birth date, time, latitude, longitude, and timezone. Returns planetary positions, houses, ASC/MC text, and a chart PNG image.

Instructions

출생 정보(날짜·시각·위경도·시간대)를 받아 서양 점성술 네이탈 차트를 계산한다. 행성별 별자리·하우스와 ASC·MC 텍스트, 그리고 네이탈 차트 PNG를 반환한다.

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>",
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "timezone": "<timezone>"
    },
    "name": "get_natal_chart"
  }
}

Input Schema

Name	Required	Description
`birthDate`	Yes	생년월일 (YYYY-MM-DD)
`birthTime`	Yes	출생시각 (HH:MM, 24시간)
`latitude`	Yes	위도 (북위 +, 남위 −)
`longitude`	Yes	경도 (동경 +, 서경 −)
`timezone`	Yes	시간대: 숫자 오프셋(예: 9, -4) 또는 IANA 존(예: "Asia/Seoul")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 19, 2026

TDQS

A3.7/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 disclose behavioral traits. It states what the tool calculates and returns but omits details like ephemeris used, precision, or whether network access is required. It is adequate but not comprehensive.

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, clear sentence that front-loads the core purpose. It is efficient but could benefit from slightly more structure, such as separating input and output details.

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 absence of output schema and siblings, the description adequately covers inputs, computation, and outputs (text and PNG). It is complete enough for an agent to understand and use the tool correctly.

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%, meaning the schema already documents all parameters. The description adds no additional meaning beyond the schema descriptions, 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.

Purpose5/5

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

The description clearly states the tool calculates a Western astrology natal chart from birth information, specifying inputs and outputs. It uses a specific verb ('calculate') and resource ('natal chart'), and distinguishes the tool's purpose without needing sibling differentiation.

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 implies usage for natal chart calculation but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives. No siblings are provided, so the need is reduced, but the dimension expects some guidance.

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_natal_chartA