astroway-mcp

Official

by astroway

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Full Chart (deprecated)

astroway_ziwei_full_chart

Read-onlyIdempotent

Generate a Zi Wei Dou Shu year pillar with animal sign and a 12-palace overview from a birth date. Note: this endpoint is deprecated and returns the same chart for every date.

Instructions

Deprecated 2026-09-08, sunset 2027-11-26. Year pillar + animal + a 12-palace overview, identical for every birth date. Use POST /ziwei/chart, which actually places the stars.

[Group: Zi Wei Dou Shu (Purple Star)] [Endpoint: POST /v1/ziwei/full-chart] [Required: date] [Cost: 5 credits (Tier ½)]

Input Schema

Name	Required	Description
`date`	Yes
`time`	No
`timezone`	No	IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
`timezoneOffset`	No	Ignored when timezone is sent.

Output Schema

Name	Required	Description	Default
`notes`	No
`animal`	No
`palaces`	No
`solarYear`	No
`disclaimer`	No
`yearPillar`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.6.0Oct 24, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations cover read-only safety, but the description adds what they cannot: the output is invariant to birth date, the tool is deprecated with a hard sunset date, and each call costs 5 credits. These are exactly the facts an agent needs to avoid wasting a paid call on meaningless data.

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?

Deprecation and the redirect are front-loaded in the first two sentences. The bracketed metadata block is mildly redundant ('Required: date' restates the schema) but the cost line earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, and the description still summarizes the payload while covering deprecation, replacement, and pricing. Nothing needed to decide whether to call it is missing.

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 coverage is 50% (timezone is richly documented in-schema; date and time are not). The description only repeats 'Required: date' without adding format or meaning, and notably never explains that time/timezone have no effect given the date-invariant output. It neither compensates nor misleads.

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?

States a specific resource and its contents ('Year pillar + animal + a 12-palace overview') and goes further by declaring the data is degenerate ('identical for every birth date'). This distinguishes it from astroway_ziwei_chart and astroway_ziwei_twelve_palaces without opening a schema.

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

Usage Guidelines5/5

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

Explicitly says not to use it and names the replacement ('Use POST /ziwei/chart, which actually places the stars'), plus deprecation and sunset dates. Both the when-not and the alternative are stated outright.

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

Deploy Server