Skip to main content
Glama
astroway

astroway-mcp

Official
by astroway

Four Transformations (四化)

astroway_ziwei_four_transformations
Read-onlyIdempotent

Computes the four Zi Wei transformations (化禄, 化权, 化科, 化忌) from a birth date's year stem, returning every school's reading for the disputed 戊, 庚 and 壬 stems.

Instructions

The four stars activated by the birth year stem: 化禄 fortune, 化权 authority, 化科 repute, 化忌 obstruction. The one part of Zi Wei computable without star placement. Seven stems are agreed across traditions; for the three that are not (戊 庚 壬) every school reading ships in schoolVariants, and school switches the headline answer.

[Group: Zi Wei Dou Shu (Purple Star)] [Endpoint: POST /v1/ziwei/four-transformations] [Required: date] [Cost: 10 credits (Tier 1)]

Input Schema

NameRequiredDescriptionDefault
dateYes
timeNo
schoolNo
timezoneNoIANA 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.
timezoneOffsetNoIgnored when timezone is sent.

Output Schema

NameRequiredDescriptionDefault
notesNo
schoolNo
disputedNo
yearStemNo
solarYearNo
schoolVariantsNo
transformationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations cover the safe-read, idempotent profile. Beyond that the description discloses a real behavioral trait: seven stems agree across traditions while 戊/庚/壬 diverge, and every school reading ships in schoolVariants while `school` only switches the headline answer.

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?

Three sentences, front-loaded with the core definition, then the enumeration of the four stars, then the tradition-divergence caveat. Only minor weight from the Chinese-character parentheticals, which aid searchability.

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?

With an output schema present, return values needn't be described, and the important output nuance (schoolVariants) is covered. The remaining gap is that it never plainly states `date` is the birth date whose year stem is used, which the agent must infer.

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 40%, so the description must partly compensate. It explains `school` (headline selection vs schoolVariants) well, but `date` is only implied to be a birth date via 'birth year stem', and `time`/`timezoneOffset` get no treatment in the description; timezone's own schema text carries itself.

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?

States a specific resource (the four transformations 化禄/化权/化科/化忌) and that they derive from the birth year stem. It also distinguishes itself from the star-placement siblings by noting this is 'the one part of Zi Wei computable without star placement'.

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?

Usage is implied: use it when you want the four transformations for a birth year stem and don't need a full chart. The `school` note gives useful context for one parameter, but there is no explicit when-to-use/when-not versus astroway_ziwei_full_chart or the palace tools.

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